From: Brian Norris <computersforpeace@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: 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: Tue, 19 Aug 2014 11:43:03 -0700 [thread overview]
Message-ID: <20140819184303.GT18411@ld-irv-0074> (raw)
In-Reply-To: <87ppfwmxic.fsf@tassilo.jf.intel.com>
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)
I cited at least one example in which this was attempted but rejected.
(Or at least, it was semi-deliberately stalled.)
> Having -Werror anywhere in a shipping release is just plainly a bug,
> as it makes it often impossible to build on newer gcc versions.
I also feel it is misguided, for other reasons. But there are at least a
few who seem to disagree. They seem to feel it is important/necessary
for enforcing good practices during development. I'm not sure how to
bridge the disagreement, other than to provide workarounds for disabling
-Werror.
I could try sending -Werror removal patches, but I'm not confident that
will go over well.
Brian
next prev parent reply other threads:[~2014-08-19 18:43 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 [this message]
2014-08-19 20:11 ` Sam Ravnborg
2014-08-19 23:43 ` Andi Kleen
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=20140819184303.GT18411@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=andi@firstfloor.org \
--cc=dedekind1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox