[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a15ada1f-9bad-612e-e841-934bff088f38@redhat.com>
Date: Sun, 18 Oct 2020 13:07:48 -0700
From: Tom Rix <trix@...hat.com>
To: Joe Perches <joe@...ches.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Julia Lawall <julia.lawall@...ia.fr>, linux-kernel@...r.kernel.org,
cocci <cocci@...teme.lip6.fr>
Subject: Re: [PATCH] checkpatch: Allow --fix removal of unnecessary break
statements
I like!
On 10/18/20 12:49 PM, Joe Perches wrote:
> switch/case use of break after a return or goto is unnecessary.
>
> There is an existing warning for these uses, so add a --fix option too.
>
> Signed-off-by: Joe Perches <joe@...ches.com>
> ---
>
> For today's next, this would remove ~300 instances like:
>
> case FOO:
> return bar;
> break;
> or
> case FOO:
> goto bar;
> break;
>
> scripts/checkpatch.pl | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index fab38b493cef..22263b278e87 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3678,8 +3678,11 @@ sub process {
> if ($sline =~ /^\+([\t]+)break\s*;\s*$/) {
> my $tabs = $1;
> if ($prevline =~ /^\+$tabs(?:goto|return)\b/) {
could add a '|break' here to catch the couple
break;
break;
Reviewed-by: Tom Rix <trix@...hat.com>
> - WARN("UNNECESSARY_BREAK",
> - "break is not useful after a goto or return\n" . $hereprev);
> + if (WARN("UNNECESSARY_BREAK",
> + "break is not useful after a goto or return\n" . $hereprev) &&
> + $fix) {
> + fix_delete_line($fixlinenr, $rawline);
> + }
> }
> }
>
>
>
Powered by blists - more mailing lists