From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: fengguang.wu@intel.com, roger.chen@rock-chips.com,
kbuild-all@01.org, peppe.cavallaro@st.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] GMAC: fix simple_return.cocci warnings
Date: Sun, 04 Jan 2015 22:20:22 -0500 (EST) [thread overview]
Message-ID: <20150104.222022.55122203599464788.davem@davemloft.net> (raw)
In-Reply-To: <1420246005.23591.7.camel@perches.com>
From: Joe Perches <joe@perches.com>
Date: Fri, 02 Jan 2015 16:46:45 -0800
> On Sat, 2015-01-03 at 08:25 +0800, kbuild test robot wrote:
>> drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c:425:1-4: WARNING: end returns can be simpified
>>
>> Simplify a trivial if-return sequence. Possibly combine with a
>> preceding function call.
>> Generated by: scripts/coccinelle/misc/simple_return.cocci
>>
>> CC: Roger Chen <roger.chen@rock-chips.com>
>> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
>> ---
>>
>> dwmac-rk.c | 6 +-----
>> 1 file changed, 1 insertion(+), 5 deletions(-)
>>
>> --- a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c
>> +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c
>> @@ -422,11 +422,7 @@ static int rk_gmac_init(struct platform_
>> if (ret)
>> return ret;
>>
>> - ret = gmac_clk_enable(bsp_priv, true);
>> - if (ret)
>> - return ret;
>> -
>> - return 0;
>> + return gmac_clk_enable(bsp_priv, true);
>
> I think this change is not particularly better.
>
> When the pattern is multiply repeated like:
...
> I think it's better to not change the last
> test in the sequence just to minimize overall
> line count.
I think it's a wash and that both ways are about the same to me.
I won't apply this, sorry.
next prev parent reply other threads:[~2015-01-05 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201501030822.7cG5bXrm%fengguang.wu@intel.com>
2015-01-03 0:25 ` [PATCH] GMAC: fix simple_return.cocci warnings kbuild test robot
2015-01-03 0:46 ` Joe Perches
2015-01-05 3:20 ` David Miller [this message]
2015-01-06 7:13 ` Roger
2015-01-06 7:26 ` Joe Perches
2015-01-06 7:52 ` 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=20150104.222022.55122203599464788.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=roger.chen@rock-chips.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).