linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854
Date: Sun, 19 Oct 2014 21:14:51 +0100	[thread overview]
Message-ID: <20141019201451.GV12379@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CA+55aFwy1hg25p3amy1xZq58afcaNSgP+uy=UA19BSgoVpARVQ@mail.gmail.com>

On Sun, Oct 19, 2014 at 01:04:20PM -0700, Linus Torvalds wrote:
> On Sun, Oct 19, 2014 at 11:51 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >
> > Does that work for things like allnoconfig and randconfig?  I guess people
> > /could/ seed those appropriately, but that seems to be something that Olof
> > wants to avoid doing.
> 
> You can force particular config options for those, using something like
> 
>     export KCONFIG_ALLCONFIG=custom.config
> 
> and filling the custom config file with the required config setting.

Yes, this is what I meant above by "seed"ing the configurations, and it
is something I do all the time with my autobuilder here for things like
allnoconfig where I want to ensure that certain options have specific
values.

When I talked to Olof about it, he seemed to be against using the
facility in his autobuilder.  I'm not clear on why that was, but I
suspect it's because Olof wants to test real allnoconfig builds.

An alternative is we could have a HAVE_GCC_PR58854_FIX preprocessor
conditional, and pass in KCFLAGS=-DHAVE_GCC_PR58854_FIX to the kernel
to bypass the check.

Either way, I think we need Olof's input on this to say what he's
willing to do.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-10-19 20:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 21:56 [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854 Russell King
2014-10-15 22:18 ` Peter Hurley
2014-10-16  0:18   ` Russell King - ARM Linux
2014-10-16  0:44     ` Peter Hurley
2014-10-16 14:58     ` Nicolas Pitre
2014-10-17 13:41       ` Russell King - ARM Linux
2014-10-19  9:55         ` Russell King - ARM Linux
     [not found]           ` <CA+55aFw_N=E9O-7VknWTzjNgYG-tB-8736diA1r7K=50b+0czQ@mail.gmail.com>
2014-10-19 18:51             ` Russell King - ARM Linux
2014-10-19 20:04               ` Linus Torvalds
2014-10-19 20:14                 ` Russell King - ARM Linux [this message]
2014-10-19 20:28                   ` Olof Johansson
2014-10-16 10:30 ` David Laight
2014-10-16 14:29   ` Russell King - ARM Linux

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=20141019201451.GV12379@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).