From: Greg KH <gregkh@linuxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: Ruxandra Ioana Radulescu <ruxandra.radulescu@nxp.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bogdan Purcareata <bogdan.purcareata@nxp.com>,
Leo Li <leoyang.li@nxp.com>,
"stuyoder@gmail.com" <stuyoder@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] staging: fsl-mc: fix uninitialized variable use
Date: Mon, 27 Nov 2017 10:44:59 +0100 [thread overview]
Message-ID: <20171127094459.GA25753@kroah.com> (raw)
In-Reply-To: <5A1BDB08.5070808@nxp.com>
On Mon, Nov 27, 2017 at 09:31:21AM +0000, Laurentiu Tudor wrote:
>
>
> On 11/27/2017 11:08 AM, Greg KH wrote:
> > On Mon, Nov 27, 2017 at 11:01:34AM +0200, laurentiu.tudor@nxp.com wrote:
> >> From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> >>
> >> Fix this warning triggering on a powerpc build:
> >> warning: 'error' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >>
> >> Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> >> ---
> >
> > You forgot a reported-by line :(
> >
> > And I beat you by about 30 minutes to this patch, sorry about that.
>
> Sorry, I guess I'm slow on mondays before having my morning coffee. :-(
>
> > Next time always test-build your patches...
>
> I did but it didn't show up on my version of powerpc toolchain (gcc
> 4.8.1). Maybe it's too old ...
Yes, that's really old, please update to something more "modern" :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-27 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 9:01 [PATCH] staging: fsl-mc: fix uninitialized variable use laurentiu.tudor
2017-11-27 9:08 ` Greg KH
2017-11-27 9:31 ` Laurentiu Tudor
2017-11-27 9:44 ` Greg KH [this message]
2017-11-28 14:13 ` Dan Carpenter
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=20171127094459.GA25753@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bogdan.purcareata@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruxandra.radulescu@nxp.com \
--cc=stuyoder@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