From: Joe Perches <joe@perches.com>
To: Antonio Borneo <borneo.antonio@gmail.com>,
Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch: fix incorrect camelcase detection on numeric constant
Date: Thu, 27 May 2021 15:05:44 -0700 [thread overview]
Message-ID: <93eb25ab04c2f7436a49f301c2c79a49cb209c44.camel@perches.com> (raw)
In-Reply-To: <20210527214741.180449-1-borneo.antonio@gmail.com>
On Thu, 2021-05-27 at 23:47 +0200, Antonio Borneo wrote:
> The code fragment below
> int foo(int *array, int index)
> {
> return array[index & 0xFF];
> }
> triggers an incorrect camelcase detection by checking a subset of
> the hex constant:
> CHECK: Avoid CamelCase: <xFF>
> #3: FILE: test.c:3:
> + return array[index & 0xFF];
>
> This is caused by passing the whole string "array[index & 0xFF]"
> to the inner loop that iterates over a "$Ident" match.
> With no check to exclude a constant, the match iterates over
> "array", "index" and "xFF", thus the camelcase detection.
The thing there is that 0xFF is not an $Ident as it doesn't
start with _[A-Za-z] so it's not excluding constants per-se.
So, you've added the right code, but just not quite the best
commit message.
> Force the match to start at word boundary so the constants will be
> filtered-out.
Anyway, thanks and cheers, Joe
>
> Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
> ---
> scripts/checkpatch.pl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> To: Andy Whitcroft <apw@canonical.com>
> To: Joe Perches <joe@perches.com>
> To: Dwaipayan Ray <dwaipayanray1@gmail.com>
> To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Cc: linux-kernel@vger.kernel.org
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 23697a6b1eaa..f0032166dfc1 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -5656,7 +5656,7 @@ sub process {
> $var !~ /^(?:[a-z0-9_]*|[A-Z0-9_]*)?_?[a-z][A-Z](?:_[a-z0-9_]+|_[A-Z0-9_]+)?$/ &&
> #Ignore some three character SI units explicitly, like MiB and KHz
> $var !~ /^(?:[a-z_]*?)_?(?:[KMGT]iB|[KMGT]?Hz)(?:_[a-z_]+)?$/) {
> - while ($var =~ m{($Ident)}g) {
> + while ($var =~ m{\b($Ident)}g) {
> my $word = $1;
> next if ($word !~ /[A-Z][a-z]|[a-z][A-Z]/);
> if ($check) {
>
> base-commit: c4681547bcce777daf576925a966ffa824edd09d
next prev parent reply other threads:[~2021-05-27 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 21:47 Antonio Borneo
2021-05-27 22:05 ` Joe Perches [this message]
2022-06-13 10:00 ` [PATCH v2] " Antonio Borneo
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=93eb25ab04c2f7436a49f301c2c79a49cb209c44.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=borneo.antonio@gmail.com \
--cc=dwaipayanray1@gmail.com \
--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®