From: Joe Perches <joe@perches.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com
Subject: Re: [PATCH] checkpatch: add --fix option for OPEN_BRACE issues
Date: Wed, 18 Nov 2020 10:14:52 -0800 [thread overview]
Message-ID: <457730448c84136be089748bea69abd2254e3832.camel@perches.com> (raw)
In-Reply-To: <20201118124035.96976-1-dwaipayanray1@gmail.com>
On Wed, 2020-11-18 at 18:10 +0530, Dwaipayan Ray wrote:
> Brace style misuses of the following types are now
> corrected:
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -3937,9 +3937,23 @@ sub process {
> #print "pre<$pre_ctx>\nline<$line>\nctx<$ctx>\nnext<$lines[$ctx_ln - 1]>\n";
>
>
> if ($ctx !~ /{\s*/ && defined($lines[$ctx_ln - 1]) && $lines[$ctx_ln - 1] =~ /^\+\s*{/) {
> - ERROR("OPEN_BRACE",
> - "that open brace { should be on the previous line\n" .
> - "$here\n$ctx\n$rawlines[$ctx_ln - 1]\n");
> + if (ERROR("OPEN_BRACE",
> + "that open brace { should be on the previous line\n" .
> + "$here\n$ctx\n$rawlines[$ctx_ln - 1]\n") &&
> + $fix) {
> + my $line1 = $rawlines[$ctx_ln - 2];
How are you sure that in a patch context this line always starts with /^\+/ ?
> + my $line2 = $rawlines[$ctx_ln - 1];
> + fix_delete_line($ctx_ln - 2, $line1);
> + fix_delete_line($ctx_ln - 1, $line2);
> +
> + my $fixedline = rtrim($line1) . " {";
> + fix_insert_line($ctx_ln - 1, $fixedline);
> + $fixedline = $line2;
> + $fixedline =~ s/^(.\s*)\{\s*/$1\t/;
> + if ($fixedline !~ /^\+\s*$/) {
> + fix_insert_line($ctx_ln - 1, $fixedline);
> + }
> + }
next prev parent reply other threads:[~2020-11-18 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:40 Dwaipayan Ray
2020-11-18 18:14 ` Joe Perches [this message]
2020-11-18 18:33 ` Dwaipayan Ray
2020-11-18 18:39 ` Joe Perches
2020-11-18 18:45 ` Dwaipayan Ray
2020-11-18 19:58 ` Joe Perches
2020-11-18 20:22 ` Dwaipayan Ray
2020-11-18 20:39 ` Joe Perches
2020-11-18 20:52 ` Dwaipayan Ray
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=457730448c84136be089748bea69abd2254e3832.camel@perches.com \
--to=joe@perches.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@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
all inboxes | Powered by JetHome®