All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: Will Tange <bh34rt@gmail.com>,
	gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: silicom: fix 'return is not a function, parentheses are not required' in bpctl_mod.c
Date: Fri, 6 Dec 2013 02:21:40 +0300	[thread overview]
Message-ID: <20131205232140.GE5443@mwanda> (raw)
In-Reply-To: <1386284955.10003.20.camel@joe-AO722>

On Thu, Dec 05, 2013 at 03:09:15PM -0800, Joe Perches wrote:
> On Fri, 2013-12-06 at 01:50 +0300, Dan Carpenter wrote:
> > On Thu, Dec 05, 2013 at 10:23:53PM +0100, Will Tange wrote:
> > > Fixes warnings regarding redundant parantheses thrown by the checkpatch tool in bpctl_mod.c
> []
> > 	if (ret < 0)
> > 		return BP_NOT_CAP;
> > 	if (ret == 0)
> > 		return 1;
> > 	return 0;
> > 
> > More lines, but simpler to understand than the original.
> > 
> > Think of checkpatch.pl as a pointer to bad code and not that we just
> > have to silence checkpatch and move on.
> 
> So true.
> 
> If 0 is the expected ret value and 1 is the
> expected function return for not-errored use,
> I suggest changing the last bit to:
> 
> 	if (ret < 0)
> 		return BP_NOT_CAP;
> 	else if (ret > 0)
> 		return 0;
> 
> 	return 1;
> 
> so that the error conditions are done first
> and the normal return is at the bottom of
> the function.

In this function, -1 means fail, 1 means "on" and 0 means "off".  I
sorted them from lowest to highest: negative, zero and greater than
zero.

regards,
dan carpenter

  reply	other threads:[~2013-12-05 23:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 21:23 [PATCH] staging: silicom: fix 'return is not a function, parentheses are not required' in bpctl_mod.c Will Tange
2013-12-05 22:50 ` Dan Carpenter
2013-12-05 23:09   ` Joe Perches
2013-12-05 23:21     ` Dan Carpenter [this message]
2013-12-05 23:29       ` Joe Perches
2013-12-06  7:11         ` Dan Carpenter
2013-12-06  7:18           ` Joe Perches

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=20131205232140.GE5443@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=bh34rt@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.