From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org,
Vegard Nossum <vegard.nossum@gmail.com>,
Eric B Munson <ebmunson@us.ibm.com>,
Johannes Berg <johannes@sipsolutions.net>,
Dave Airlie <airlied@linux.ie>
Subject: Re: v2.6.31-7381-g7fa0772: new build warnings: kmemcheck, __deprecated, hugetlb, radeon
Date: Wed, 23 Sep 2009 10:20:46 +0300 [thread overview]
Message-ID: <84144f020909230020m3a562220x8eda4f102e452c48@mail.gmail.com> (raw)
In-Reply-To: <4AB8FC88.8020608@s5r6.in-berlin.de>
On Tue, Sep 22, 2009 at 7:34 PM, Stefan Richter
<stefanr@s5r6.in-berlin.de> wrote:
> Latest git compiles with extreme noise:
>
> In file included from include/net/inet_connection_sock.h:23,
> from include/linux/tcp.h:178,
> from include/linux/ipv6.h:215,
> from include/net/ipv6.h:16,
> from include/linux/sunrpc/clnt.h:25,
> from include/linux/nfs_fs.h:52,
> from kernel/sysctl.c:48:
> include/net/inet_sock.h: In function 'inet_reqsk_alloc':
> include/net/inet_sock.h:208: warning: ISO C90 forbids mixed declarations and
> code
>
> Vegard, this is obviously caused by commit
> 45e3ff82708c65c895d5c5882aff17ecf62a80b5.
>
> $ grep KMEMCH .config
> CONFIG_HAVE_ARCH_KMEMCHECK=y
>
> (I.e. CONFIG_KMEMCHECK is off.)
Curious, I haven't seen this before. Is it coming from the
BUILD_BUG_ON() in kmemcheck_annotate_bitfield()? I can't seem to spot
the error.
Pekka
prev parent reply other threads:[~2009-09-23 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 16:34 Stefan Richter
2009-09-23 6:39 ` Johannes Berg
2009-09-23 7:19 ` Jean Delvare
2009-09-23 7:21 ` Pekka Enberg
2009-09-23 15:13 ` Stefan Richter
2009-09-23 8:19 ` Jean Delvare
2009-09-23 7:20 ` Pekka Enberg [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=84144f020909230020m3a562220x8eda4f102e452c48@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=airlied@linux.ie \
--cc=ebmunson@us.ibm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=vegard.nossum@gmail.com \
/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
all inboxes | Powered by JetHome®