From: David Miller <davem@davemloft.net>
To: dan.carpenter@oracle.com
Cc: steve.glendinning@shawell.net, netdev@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [patch] usbnet: smsc95xx: silence an uninitialized variable warning
Date: Wed, 04 May 2016 17:00:01 -0400 (EDT) [thread overview]
Message-ID: <20160504.170001.1649317898691832917.davem@davemloft.net> (raw)
In-Reply-To: <20160504062201.GF22064@mwanda>
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Wed, 4 May 2016 09:22:01 +0300
> If the call to fn() fails then "buf" is uninitialized. Just return the
> error code in that case.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied.
Please, in the future, use a consistent subsystem prefixing scheme. In these
two patches you used "x/y:"" and "x: y:"
Thanks.
prev parent reply other threads:[~2016-05-04 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 6:22 [patch] usbnet: smsc95xx: silence an uninitialized variable warning Dan Carpenter
2016-05-04 21:00 ` David Miller [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=20160504.170001.1649317898691832917.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dan.carpenter@oracle.com \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.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;
as well as URLs for NNTP newsgroup(s).