From: Michael Neuling <mikey@neuling.org>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: fix uninitialised error in numa.c
Date: Wed, 20 Jun 2012 15:46:06 +1000 [thread overview]
Message-ID: <27235.1340171166@neuling.org> (raw)
In-Reply-To: <20120620053808.GD11330@thor.bakeyournoodle.com>
Tony Breeds <tony@bakeyournoodle.com> wrote:
> On Wed, Jun 20, 2012 at 02:17:47PM +1000, Michael Neuling wrote:
> > chroma_defconfig currently gives me this with gcc 4.6:
> > arch/powerpc/mm/numa.c:638:13: error: 'dm' may be used uninitialized in this function [-Werror=uninitialized]
> >
> > It's a bogus warning since of_get_drconf_memory() only writes it
> > anyway.
> >
> > Signed-off-by: Michael Neuling <mikey@neuling.org>
> > cc: stable@kernel.org
> > ---
> > Also affects 3.4 and 3.3 stable.
> >
> > diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
> > index 5ca3a15..880acde 100644
> > --- a/arch/powerpc/mm/numa.c
> > +++ b/arch/powerpc/mm/numa.c
> > @@ -637,7 +637,7 @@ static inline int __init read_usm_ranges(const u32 **usm)
> > */
> > static void __init parse_drconf_memory(struct device_node *memory)
> > {
> > - const u32 *dm, *usm;
> > + const u32 *dm = NULL, *usm;
>
> Woot bikeshed! I think that's what the uninitialized_var() macro is for.
Doesn't work here. Produces the same error.
Mikey
next prev parent reply other threads:[~2012-06-20 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 4:17 [PATCH] powerpc: fix uninitialised error in numa.c Michael Neuling
2012-06-20 5:38 ` Tony Breeds
2012-06-20 5:46 ` Michael Neuling [this message]
2012-06-20 6:01 ` Michael Neuling
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=27235.1340171166@neuling.org \
--to=mikey@neuling.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tony@bakeyournoodle.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;
as well as URLs for NNTP newsgroup(s).