From: Arnd Bergmann <arnd@arndb.de>
To: kernel-build-reports@lists.linaro.org
Cc: Ralf Baechle <ralf@linux-mips.org>,
Mark Brown <broonie@kernel.org>,
linux-mips@linux-mips.org
Subject: Re: next build: 198 builds: 4 failed, 194 passed, 7 errors, 82 warnings (next-20161214)
Date: Thu, 15 Dec 2016 09:02:17 +0100 [thread overview]
Message-ID: <2139236.OXpNvTk27O@wuerfel> (raw)
In-Reply-To: <20161215032241.GB15191@linux-mips.org>
On Thursday, December 15, 2016 4:22:41 AM CET Ralf Baechle wrote:
>
> Some configurations, in particular new cores or architecture variants
> may require vendor tool- chains or patches until support makes it upstream.
> I wonder if for the benefit of automated build testing we should tag
> kernel configurations with a special CONFIG_ symbol to indicate they need
> non-standard tools? That would allow build testing to detect and
> possibly skip such configuration.
I think that this ties in with a discussion we recently had about moving
toolchain feature detection from Makefiles into Kconfig, which can
then probably handle this better. We just need to find someone who
can hack this up into Kconfig.
Arnd
next prev parent reply other threads:[~2016-12-15 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58510536.04c7190a.4a2fb.ae5c@mx.google.com>
2016-12-14 13:52 ` next build: 198 builds: 4 failed, 194 passed, 7 errors, 82 warnings (next-20161214) Mark Brown
2016-12-14 16:06 ` Ralf Baechle
2016-12-14 17:45 ` Mark Brown
2016-12-14 20:56 ` Arnd Bergmann
2016-12-14 20:56 ` Arnd Bergmann
2016-12-15 3:22 ` Ralf Baechle
2016-12-15 8:02 ` Arnd Bergmann [this message]
2016-12-15 11:00 ` Mark Brown
2016-12-16 0:56 ` Ralf Baechle
2016-12-16 12:19 ` Mark Brown
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=2139236.OXpNvTk27O@wuerfel \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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.