From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] buildman: README: add links for toolchains not available on kernel.org
Date: Thu, 12 Nov 2015 03:19:18 +0100 [thread overview]
Message-ID: <201511120319.18960.marex@denx.de> (raw)
In-Reply-To: <5643E855.9010900@wytron.com.tw>
On Thursday, November 12, 2015 at 02:16:05 AM, Thomas Chou wrote:
> Hi Marek,
Hi!
> On 2015?11?11? 23:54, Marek Vasut wrote:
> > On Wednesday, November 11, 2015 at 02:37:08 PM, Thomas Chou wrote:
> >> Add links for toolchains not available on kernel.org.
> >>
> >> The sh4 toolchains from kernel.org dose not work for some boards,
> >> so use the sh from Sourcery.
> >>
> >> Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
> >
> > Wouldn't it instead make more sense to get kernel.org to mirror those
> > toolchains ? The links might not last forever, but I think kernel.org
> > is not gonna go belly-up any soon.
>
> Agree. But I think it will be helpful to offer these links when it is
> missing or not working on kernel.org.
Sure, but if it's missing on k.org, it should just be added there too.
> I realized now that buildman is an effective and must-have tool. Every
> developer should run buildman before submitting patches, though it does
> take hours to run. The problem is that some toolchains are not easily
> found until looking into tools/moveconfig.py. So we should make it
> available.
Yeah.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-11-12 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 13:37 [U-Boot] [PATCH] buildman: README: add links for toolchains not available on kernel.org Thomas Chou
2015-11-11 15:54 ` Marek Vasut
2015-11-12 1:16 ` Thomas Chou
2015-11-12 2:19 ` Marek Vasut [this message]
2015-11-12 2:23 ` Bin Meng
2015-11-13 18:14 ` Simon Glass
2015-12-11 13:24 ` Simon Glass
2015-11-12 1:29 ` [U-Boot] [PATCH v2] " Thomas Chou
2015-11-12 2:13 ` Bin Meng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201511120319.18960.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.