From: Torsten Duwe <duwe@lst.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Ian Munsie <imunsie@au1.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Michael Neuling <mikey@neuling.org>,
Anton Blanchard <anton@au1.ibm.com>,
Michael Ellerman <michaele@au1.ibm.com>
Subject: Re: [PATCH] cxl: Fix build failure due to -Wunused-variable behaviour change
Date: Tue, 1 Dec 2015 15:47:41 +0100 [thread overview]
Message-ID: <20151201144741.GA5509@lst.de> (raw)
In-Reply-To: <1448494913.22705.3.camel@ellerman.id.au>
On Thu, Nov 26, 2015 at 10:41:53AM +1100, Michael Ellerman wrote:
> On Wed, 2015-11-25 at 17:16 +0100, Torsten Duwe wrote:
> > On Tue, Sep 15, 2015 at 03:48:34PM +1000, Ian Munsie wrote:
> > > --- a/drivers/misc/cxl/Makefile
> > > +++ b/drivers/misc/cxl/Makefile
> > > @@ -1,4 +1,4 @@
> > > -ccflags-y := -Werror
> > > +ccflags-y := -Werror -Wno-unused-const-variable
> >
> > JFYI, my gcc-4.3 does not like this switch.
> > What's the minimum compiler version to build this code?
>
> I build everything with gcc 4.4.4, so if it breaks with that I will notice.
>
> Does it work if you wrap it in cc-option? eg:
>
> ccflags-y := -Werror $(call cc-option,-Wno-unused-const-variable)
Yes, now it builds. It also looks cleaner to me: compilers which check
for "unused-const-variable"s should have this switch and the check is disabled.
All other (known :) warnings error out.
Torsten
prev parent reply other threads:[~2015-12-01 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 5:48 [PATCH] cxl: Fix build failure due to -Wunused-variable behaviour change Ian Munsie
2015-09-17 5:13 ` Michael Ellerman
2015-11-25 16:16 ` [PATCH] " Torsten Duwe
2015-11-25 22:58 ` Anton Blanchard
2015-11-25 23:41 ` Michael Ellerman
2015-12-01 14:47 ` Torsten Duwe [this message]
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=20151201144741.GA5509@lst.de \
--to=duwe@lst.de \
--cc=anton@au1.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michaele@au1.ibm.com \
--cc=mikey@neuling.org \
--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;
as well as URLs for NNTP newsgroup(s).