From: Anish Bhatt <anish@chelsio.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] checkpatch: Warn on unnecessary void function return statements
Date: Tue, 17 Jun 2014 12:37:25 -0700 [thread overview]
Message-ID: <53A098F5.6040104@chelsio.com> (raw)
In-Reply-To: <1402970429.2797.3.camel@joe-AO725>
On 06/16/2014 07:00 PM, Joe Perches wrote:
> On Mon, 2014-06-16 at 17:44 -0700, Anish Bhatt wrote:
>> My code has multiple exit lables:
>> void function(void)
>> {
>> ...
>>
>> if (err1)
>> goto exit1;
>> ...
>> if (err2)
>> goto exit2;
>>
>> ...
>> return; /* Good return, no errors */
>> exit1:
>> printk(err1);
>> return;
>> exit2:
>> printk(err2);
>> }
>>
>> The single tabbed return was required to prevent the good return & err1
>> messages cascading down. The extra exit label with a noop looks weird,
>> but is passing checkpatch.pl --strict, so I will go with that, thanks.
>> -Anish
>>
>
> Hmm, those return uses seem reasonable
> to me.
>
> Perhaps the test should warn only on
> this specific 3 line sequence:
>
> [any line but a label]
> return;
> }
>
> Andrew? Anyone else? Opinions?
>
I think simply
return;
}
should trigger the warning. If you are using a label just to exit, you could just do it in-place (though possibly someone might want to a goto instead of multiple returns)
-Anish
next prev parent reply other threads:[~2014-06-17 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 16:58 [PATCH] checkpatch: Warn on unnecessary void function return statements Joe Perches
2014-06-16 23:28 ` Anish Bhatt
2014-06-17 0:28 ` Joe Perches
2014-06-17 0:44 ` Anish Bhatt
2014-06-17 2:00 ` Joe Perches
2014-06-17 3:16 ` Sachin Kamat
2014-06-17 3:25 ` Joe Perches
2014-06-17 3:35 ` Sachin Kamat
2014-06-17 19:37 ` Anish Bhatt [this message]
2014-06-18 17:44 ` [PATCH V2] " Joe Perches
2014-06-18 19:59 ` Anish Bhatt
2014-06-19 20:18 ` Andrew Morton
2014-06-19 20:28 ` 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=53A098F5.6040104@chelsio.com \
--to=anish@chelsio.com \
--cc=akpm@linux-foundation.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.