All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-kbuild@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Overriding -Werror
Date: Wed, 20 Aug 2014 01:43:59 +0200	[thread overview]
Message-ID: <20140819234359.GJ4120@two.firstfloor.org> (raw)
In-Reply-To: <20140819201129.GA24217@ravnborg.org>

On Tue, Aug 19, 2014 at 10:11:30PM +0200, Sam Ravnborg wrote:
> On Tue, Aug 19, 2014 at 06:15:07AM -0700, Andi Kleen wrote:
> > Brian Norris <computersforpeace@gmail.com> writes:
> > >
> > > 4. better ideas?
> > 
> > Just send patches to remove -Werror in all architectures
> > as a tree sweep (and anywhere else where someone misguided add it)
> In arch/sparc/ we have -Werror and this has never troubled us.
> In fact more than once people had tried to provide sloppy code that
> failed due to -Werror so it got fixed up front.

It's a major mistake to not support future gccs for released source.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2014-08-19 23:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 22:21 Overriding -Werror Brian Norris
2014-08-15  9:30 ` Jeff Kirsher
2014-08-15 19:33   ` Brian Norris
2014-08-16  3:36     ` Mark D Rustad
2014-08-16  4:34       ` Brian Norris
2014-08-17  6:19         ` Mark D Rustad
2014-08-15 15:33 ` Lennart Sorensen
2014-08-15 16:51   ` Geert Uytterhoeven
2014-08-19 13:15 ` Andi Kleen
2014-08-19 18:43   ` Brian Norris
2014-08-19 20:11   ` Sam Ravnborg
2014-08-19 23:43     ` Andi Kleen [this message]
2014-08-20  5:10       ` Sam Ravnborg

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=20140819234359.GJ4120@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=sam@ravnborg.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.