From: Daniel Axtens <dja@axtens.net>
To: Arnd Bergmann <arnd@arndb.de>, linuxppc-dev@lists.ozlabs.org
Cc: Brian Norris <computersforpeace@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Michael Neuling <mikey@neuling.org>,
Anton Blanchard <anton@au1.ibm.com>,
linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.com>,
Ian Munsie <imunsie@au1.ibm.com>
Subject: Re: Build failure: -Wno-unused-const-variable DNE on old GCC
Date: Fri, 08 Jan 2016 09:51:35 +1100 [thread overview]
Message-ID: <87oacx6m14.fsf@gamma.ozlabs.ibm.com> (raw)
In-Reply-To: <10821353.mAlCTdTQBC@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
Hi Arnd,
Thanks for your patch.
Acked-by: Daniel Axtens <dja@axtens.net>
> Alternatively, remove the -Werror. We occasionally get people that add this
> flag to a Makefile, but it tends to cause more trouble whenever a new
> gcc version arrives.
Speaking up as the person who added -Werror to cxl, I'd really rather
it stayed. There are a number of reasons I think this. Here's the first
three that came to mind.
- cxl is powerpc specific (and always will be for deep seated hardware
reasons), and is handled through the powerpc tree. arch/powerpc
compiles with -Werror, and as part of the powerpc ecosystem, cxl
should too.
- It forces cxl developers to a higher standard. cxl has already had
more than it's fair share of incredibly difficult to debug issues,
so any way we can reduce the risk of errors going in makes our lives
(and our end-users lives) better.
- I am (and I'm quite confident the other cxl people are) quite happy to
send patches to fix build-breaking issues such as this. Indeed, I
would have, except you sent it during the Australian night :)
If it's really super-duper important we can consider putting it behind a
config guard, but I'd really rather not.
Regards,
Daniel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 859 bytes --]
next prev parent reply other threads:[~2016-01-07 22:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 18:54 Brian Norris
2016-01-07 19:37 ` Joe Perches
2016-01-07 19:44 ` Michal Marek
2016-01-07 19:57 ` Joe Perches
2016-01-07 20:18 ` Brian Norris
2016-01-07 20:38 ` [PATCH] misc: cxl: fix build for GCC 4.6.x Brian Norris
2016-01-08 2:12 ` Michael Ellerman
2016-01-30 14:20 ` Build failure: -Wno-unused-const-variable DNE on old GCC Maciej W. Rozycki
2016-01-30 17:37 ` Joe Perches
2016-01-07 20:25 ` Arnd Bergmann
2016-01-07 22:51 ` Daniel Axtens [this message]
2016-01-07 23:02 ` Brian Norris
2016-01-08 1:31 ` Ian Munsie
2016-01-08 2:07 ` Brian Norris
2016-01-08 2:16 ` Michael Ellerman
2016-01-08 10:14 ` David Laight
2016-01-08 1:33 ` Ian Munsie
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=87oacx6m14.fsf@gamma.ozlabs.ibm.com \
--to=dja@axtens.net \
--cc=anton@au1.ibm.com \
--cc=arnd@arndb.de \
--cc=computersforpeace@gmail.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mmarek@suse.com \
--cc=mpe@ellerman.id.au \
/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
Powered by JetHome