From: Fengguang Wu <wfg@linux.intel.com>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: include/net/netlink.h:497:41: warning: ‘reply_nlh’ may be used uninitialized in this function [-Wuninitialized]
Date: Fri, 15 Jun 2012 09:55:31 +0800 [thread overview]
Message-ID: <20120615015531.GA8488@localhost> (raw)
In-Reply-To: <20120614083057.GA29738@canuck.infradead.org>
On Thu, Jun 14, 2012 at 04:30:57AM -0400, Thomas Graf wrote:
> On Thu, Jun 14, 2012 at 10:07:08AM +0800, wfg@linux.intel.com wrote:
> > FYI: there are new compile warnings show up in
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> > head: 0450243096de90ff51c3a6c605410c5e28d79f8d
> > commit: 33a03aadb52fa05d28aba6d8f0c03c7b3b905897 [464/472] dcbnl: Prepare framework to shorten handling functions
> > config: x86_64-randconfig-net3 (attached as .config)
> >
> > All related error/warning messages are:
> >
> > net/dcb/dcbnl.c: In function ‘dcb_doit’:
> > include/net/netlink.h:497:41: warning: ‘reply_nlh’ may be used uninitialized in this function [-Wuninitialized]
> > net/dcb/dcbnl.c:1975:19: note: ‘reply_nlh’ was declared here
>
> gcc 4.6.3 on my system doesn't complain about this. I'm sending a patch.
I'm running gcc 4.6.2 and will upgrade it. Good to know gcc improved on this!
Thanks,
Fengguang
next prev parent reply other threads:[~2012-06-15 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 2:07 include/net/netlink.h:497:41: warning: ‘reply_nlh’ may be used uninitialized in this function [-Wuninitialized] wfg
2012-06-14 8:30 ` Thomas Graf
2012-06-15 1:55 ` Fengguang Wu [this message]
2012-06-14 8:34 ` [PATCH] dcbnl: Silence harmless gcc warning about uninitialized reply_nlh Thomas Graf
2012-06-14 8:46 ` David Miller
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=20120615015531.GA8488@localhost \
--to=wfg@linux.intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).