From: Joe Perches <joe@perches.com>
To: simran singhal <singhalsimran0@gmail.com>, gregkh@linuxfoundation.org
Cc: lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 4/5] staging: sm750fb: Remove unnecessary else after return
Date: Mon, 27 Feb 2017 19:31:08 +0000 [thread overview]
Message-ID: <1488223868.25838.10.camel@perches.com> (raw)
In-Reply-To: <1488219268-3006-4-git-send-email-singhalsimran0@gmail.com>
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
[]
> diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c b/drivers/staging/sm750fb/ddk750_swi2c.c
[]
> @@ -295,8 +294,7 @@ static long sw_i2c_write_byte(unsigned char data)
>
> if (i < 0xff)
> return 0;
> - else
> - return -1;
> + return -1;
Assuming -1 is some sort of error,
it'd be a more common style to use
if (i >= 0xff)
return -1;
return 0;
Looking at the code, it might make
sense to use something like:
/* SDA still != 0 */
if (i >= 0xff)
return -1;
return 0;
}
next prev parent reply other threads:[~2017-02-27 19:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 18:26 [PATCH 1/5] staging: lustre: Remove unnecessary else after return simran singhal
2017-02-27 18:26 ` [PATCH 2/5] staging: rtl8192u: " simran singhal
2017-02-27 21:25 ` [Outreachy kernel] " Julia Lawall
2017-02-27 18:26 ` [PATCH 3/5] staging: rtl8712: " simran singhal
2017-02-27 21:19 ` [Outreachy kernel] " Julia Lawall
2017-02-28 19:29 ` SIMRAN SINGHAL
2017-02-28 19:19 ` Julia Lawall
2017-02-27 18:26 ` [PATCH 4/5] staging: sm750fb: " simran singhal
2017-02-27 19:31 ` Joe Perches [this message]
2017-02-27 20:34 ` SIMRAN SINGHAL
2017-02-27 21:15 ` [Outreachy kernel] " Julia Lawall
2017-02-28 19:08 ` SIMRAN SINGHAL
2017-02-28 19:00 ` Julia Lawall
2017-02-28 19:17 ` SIMRAN SINGHAL
2017-02-27 18:26 ` [PATCH 5/5] staging: gdm724x: " simran singhal
2017-02-27 19:41 ` Joe Perches
2017-02-27 20:31 ` SIMRAN SINGHAL
2017-02-28 19:23 ` SIMRAN SINGHAL
2017-02-28 19:18 ` [Outreachy kernel] " Julia Lawall
2017-02-28 19:18 ` Joe Perches
2017-02-28 19:21 ` [Outreachy kernel] " Julia Lawall
2017-02-27 19:25 ` [PATCH 1/5] staging: lustre: " Joe Perches
2017-02-27 20:33 ` SIMRAN SINGHAL
2017-02-27 20:43 ` Joe Perches
2017-02-28 19:13 ` SIMRAN SINGHAL
2017-02-28 19:14 ` [Outreachy kernel] " Julia Lawall
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=1488223868.25838.10.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=singhalsimran0@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;
as well as URLs for NNTP newsgroup(s).