From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Date: Mon, 27 Feb 2017 20:43:20 +0000 Subject: Re: [PATCH 1/5] staging: lustre: Remove unnecessary else after return Message-Id: <1488228200.25838.14.camel@perches.com> List-Id: References: <1488219268-3006-1-git-send-email-singhalsimran0@gmail.com> <1488223529.25838.8.camel@perches.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: SIMRAN SINGHAL Cc: Greg KH , lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, outreachy-kernel@googlegroups.com On Tue, 2017-02-28 at 01:51 +0530, SIMRAN SINGHAL wrote: > On Tue, Feb 28, 2017 at 12:55 AM, Joe Perches wrote: > > 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. > > > > checkpatch doesn't actually warn for this style > > > > if (foo) > > return bar; > > else > > return baz; > > > > ok, My bad > so, I have to change commit message as checkpatch doesn't warn for this style. Perhaps better would be to leave them unchanged instead. > > > diff --git a/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c b/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c [] > > > @@ -1806,8 +1806,7 @@ ksocknal_close_matching_conns(struct lnet_process_id id, __u32 ipaddr) > > > > > > if (!count) > > > return -ENOENT; > > > - else > > > - return 0; > > > + return 0; There might be a case for this one. error returns are generally in the form { [...] err = func(...); if (err < 0) return err; return 0; }