From: Joe Perches <joe@perches.com>
To: Dmitry Kravkov <Dmitry.Kravkov@qlogic.com>,
Julia Lawall <julia.lawall@lip6.fr>
Cc: Ariel Elior <ariel.elior@qlogic.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bnx2x: Convert return 0 to return rc
Date: Fri, 16 May 2014 13:12:24 -0700 [thread overview]
Message-ID: <1400271144.12373.21.camel@joe-AO725> (raw)
In-Reply-To: <87B4DDAD5EAFA041BDC28F314593782D0172ECD7@avmb3.qlogic.org>
On Fri, 2014-05-16 at 12:02 +0000, Dmitry Kravkov wrote:
> > -----Original Message-----
> > From: netdev-owner@vger.kernel.org [mailto:netdev-
> > owner@vger.kernel.org] On Behalf Of Joe Perches
> > Sent: Friday, May 16, 2014 9:52 AM
> > To: Ariel Elior; Dmitry Kravkov
> > Cc: netdev; linux-kernel
> > Subject: [PATCH] bnx2x: Convert return 0 to return rc
> >
> > These "return 0;" uses seem wrong as there are
> > rc variables where error return values are set
> > but unused.
[]
> Thanks Joe for catching this!
>
> Acked-by: Dmitry Kravkov <Dmitry.Kravkov@qlogic.com>
Hello Dmitry.
Couple things actually:
o Could you please update the MAINTAINER entry for
BNX2X? Ariel Elior's email address is still listed
as @broadcom and that seems to bounce.
o I found this via coccinelle actually.
Julia Lawall submitted a patch to remove unused
netdev_priv calls. I modified that to check for
any expression that returns an unused value and
found this and many others. There are a lot of
false positives though.
@@
local idexpression x;
expression E;
@@
-x = E;
... when != x
next prev parent reply other threads:[~2014-05-16 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 6:51 [PATCH] bnx2x: Convert return 0 to return rc Joe Perches
2014-05-16 12:02 ` Dmitry Kravkov
2014-05-16 20:12 ` Joe Perches [this message]
2014-05-16 20:49 ` David Miller
2014-05-19 0:51 ` 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=1400271144.12373.21.camel@joe-AO725 \
--to=joe@perches.com \
--cc=Dmitry.Kravkov@qlogic.com \
--cc=ariel.elior@qlogic.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--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