From: Darren Hart <dvhart@infradead.org>
To: "Chen, Hanxiao" <chenhanxiao@cn.fujitsu.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "acpi4asus-user@lists.sourceforge.net"
<acpi4asus-user@lists.sourceforge.net>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
Corentin Chary <corentin.chary@gmail.com>
Subject: Re: [PATCH] eeepc-laptop: fix a Wuninitialized warning
Date: Mon, 15 Sep 2014 10:40:48 -0700 [thread overview]
Message-ID: <20140915174048.GA59389@vmdeb7> (raw)
In-Reply-To: <5871495633F38949900D2BF2DC04883E5A8782@G08CNEXMBPEKD02.g08.fujitsu.local>
On Mon, Sep 15, 2014 at 02:16:35AM +0000, Chen, Hanxiao wrote:
>
>
> > -----Original Message-----
> > From: Darren Hart [mailto:dvhart@infradead.org]
> > On Fri, Sep 12, 2014 at 04:44:26PM +0800, Chen Hanxiao wrote:
> >
> > Hi Chen,
> >
> > I don't see such a warning with gcc 4.9.1. Which compiler are you using?
> >
>
> I'm using gcc 4.8.2 on Fedora20.
> Should we ignore the warning of old version of gcc?
>
> If not, I'll resend this with a detail commit message.
In my experience, we do not add workarounds for buggy compilers reporting bogus
unitialized variable warnings because those workarounds effectively mask
legitimate uninitialized variable cases.
Rafael, do you agree?
Thanks,
Darren
>
> Thanks for your help.
>
> - Chen
>
> > Please include these sorts of details (which compiler, etc.) when submitting
> > patches. I will never merge a patch without a complete commit message.
> >
> >
> > > Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
> > > ---
> > > drivers/platform/x86/eeepc-laptop.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/platform/x86/eeepc-laptop.c
> > b/drivers/platform/x86/eeepc-laptop.c
> > > index bd533c2..738fc0c 100644
> > > --- a/drivers/platform/x86/eeepc-laptop.c
> > > +++ b/drivers/platform/x86/eeepc-laptop.c
> > > @@ -276,7 +276,7 @@ static ssize_t store_sys_acpi(struct device *dev, int cm,
> > > const char *buf, size_t count)
> > > {
> > > struct eeepc_laptop *eeepc = dev_get_drvdata(dev);
> > > - int rv, value;
> > > + int rv, value = -1;
> > >
> > > rv = parse_arg(buf, count, &value);
> >
> > Inspecting the code, I don't see how this could possibly result in the use of
> > an
> > uninitialized variable.
> >
> > --
> > Darren Hart
> > Intel Open Source Technology Center
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2014-09-15 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 8:44 [PATCH] eeepc-laptop: fix a Wuninitialized warning Chen Hanxiao
2014-09-12 20:53 ` Darren Hart
2014-09-15 2:16 ` Chen, Hanxiao
2014-09-15 17:40 ` Darren Hart [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=20140915174048.GA59389@vmdeb7 \
--to=dvhart@infradead.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=chenhanxiao@cn.fujitsu.com \
--cc=corentin.chary@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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