From: Jean Delvare <khali@linux-fr.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the i2c tree
Date: Wed, 17 Feb 2010 09:34:46 +0100 [thread overview]
Message-ID: <20100217093446.2e610f45@hyperion.delvare> (raw)
In-Reply-To: <20100217113855.7ebf3d39.sfr@canb.auug.org.au>
On Wed, 17 Feb 2010 11:38:55 +1100, Stephen Rothwell wrote:
> Hi Jean,
>
> After merging the i2c tree, today's linux-next build (powerpc
> ppc64_defconfig) produced warnings like this:
>
> In file included from include/linux/bitops.h:17,
> from include/linux/kernel.h:15,
> from drivers/i2c/i2c-boardinfo.c:19:
> arch/powerpc/include/asm/bitops.h:226: warning: declaration of 'ffs' shadows a built-in function
>
> The x86_64 allmodconfig produces similar:
>
> In file included from include/linux/bitops.h:17,
> from include/linux/kernel.h:15,
> from next/drivers/i2c/i2c-boardinfo.c:19:
> arch/x86/include/asm/bitops.h:395: warning: declaration of 'ffs' shadows a built-in function
>
> Exposed by commit fa4f62e9f3a85490aebe8857e2208c37da851ce3 ("i2c: Build
> core and algo drivers with -Wshadow").
>
> Jean, I realise that these warnings are not something your tree has
> added, just that you have exposed them. They are a bit annoying,
> though. I am using gcc v4.4.3.
Oh well. I had the hope that at least the header files were
Wshadow-compliant so it could be enabled for selected source files. Not
getting any warning on my own system when I tried, I thought it was
fine... If it is not, then I'll just remove this patch from my tree.
Sorry for the noise and thanks for reporting.
--
Jean Delvare
next prev parent reply other threads:[~2010-02-17 8:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 0:38 linux-next: build warning after merge of the i2c tree Stephen Rothwell
2010-02-17 8:34 ` Jean Delvare [this message]
2010-03-28 23:54 Stephen Rothwell
2010-03-29 13:21 ` Jean Delvare
2010-03-29 14:12 ` Stephen Rothwell
2014-03-06 2:50 Stephen Rothwell
2017-06-05 1:11 Stephen Rothwell
2017-06-15 1:34 ` Stephen Rothwell
2017-06-15 7:02 ` Wolfram Sang
2017-06-15 8:48 ` Stephen Rothwell
2019-06-11 0:25 Stephen Rothwell
2019-06-12 8:19 ` Wolfram Sang
2019-06-12 11:02 ` Mauro Carvalho Chehab
2019-06-12 11:09 ` Wolfram Sang
2019-06-12 11:48 ` Mauro Carvalho Chehab
2019-06-12 12:04 ` Wolfram Sang
2019-06-12 12:32 ` Mauro Carvalho Chehab
2019-06-12 13:15 ` Stephen Rothwell
2019-06-12 13:24 ` Wolfram Sang
2019-08-02 3:21 Stephen Rothwell
2019-08-02 6:04 ` Uwe Kleine-König
2021-08-18 6:29 Stephen Rothwell
2021-08-18 6:54 ` Jie Deng
2021-08-18 7:04 ` Stephen Rothwell
2021-08-18 7:13 ` Jie Deng
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=20100217093446.2e610f45@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.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).