From: Clement LE GOFFIC <clement.legoffic@foss.st.com>
To: Antonio Borneo <antonio.borneo@foss.st.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Clément Léger" <clement.leger@bootlin.com>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2] checkpatch: use utf-8 match for spell checking
Date: Tue, 20 May 2025 15:14:02 +0200 [thread overview]
Message-ID: <e1bd523b-e7da-41eb-ad1a-a56488c4f0cd@foss.st.com> (raw)
In-Reply-To: <02e9e9c5-449a-48ae-88a7-0483895cd4bf@foss.st.com>
On 5/6/24 14:07, Clement LE GOFFIC wrote:
> Hello,
>
> A gentle reminder to review this patch.
>
> Best regards,
>
> Clément
>
> On 1/2/24 17:10, Antonio Borneo wrote:
>> The current code that checks for misspelling verifies, in a more
>> complex regex, if $rawline matches [^\w]($misspellings)[^\w]
>>
>> Being $rawline a byte-string, a utf-8 character in $rawline can
>> match the non-word-char [^\w].
>> E.g.:
>> ./scripts/checkpatch.pl --git 81c2f059ab9
>> WARNING: 'ment' may be misspelled - perhaps 'meant'?
>> #36: FILE: MAINTAINERS:14360:
>> +M: Clément Léger <clement.leger@bootlin.com>
>> ^^^^
>>
>> Use a utf-8 version of $rawline for spell checking.
>>
>> Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
>> Reported-by: Clément Le Goffic <clement.legoffic@foss.st.com>
>> ---
>> Changes in v2:
>> - use $rawline_utf8 also in the while-loop's body;
>> - fix path of checkpatch in the commit message.
>> ---
>> scripts/checkpatch.pl | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index 25fdb7fda112..2d122d232c6d 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -3477,9 +3477,10 @@ sub process {
>> # Check for various typo / spelling mistakes
>> if (defined($misspellings) &&
>> ($in_commit_log || $line =~ /^(?:\+|Subject:)/i)) {
>> - while ($rawline =~ /(?:^|[^\w\-'`])($misspellings)(?:
>> [^\w\-'`]|$)/gi) {
>> + my $rawline_utf8 = decode("utf8", $rawline);
>> + while ($rawline_utf8 =~ /(?:^|[^\w\-'`])($misspellings)
>> (?:[^\w\-'`]|$)/gi) {
>> my $typo = $1;
>> - my $blank = copy_spacing($rawline);
>> + my $blank = copy_spacing($rawline_utf8);
>> my $ptr = substr($blank, 0, $-[1]) . "^" x
>> length($typo);
>> my $hereptr = "$hereline$ptr\n";
>> my $typo_fix = $spelling_fix{lc($typo)};
>>
>> base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
Hi,
Is it just due to -ENOTIME for the maintainers, or are there doubts
about this patch? (inspired from a response of Uwe).
Clément
prev parent reply other threads:[~2025-05-20 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 9:43 [PATCH] " Antonio Borneo
2023-12-12 19:07 ` Joe Perches
2024-01-02 16:04 ` Antonio Borneo
2024-01-02 16:10 ` [PATCH v2] " Antonio Borneo
2024-05-06 12:07 ` Clement LE GOFFIC
2025-05-20 13:14 ` Clement LE GOFFIC [this message]
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=e1bd523b-e7da-41eb-ad1a-a56488c4f0cd@foss.st.com \
--to=clement.legoffic@foss.st.com \
--cc=antonio.borneo@foss.st.com \
--cc=apw@canonical.com \
--cc=clement.leger@bootlin.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--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®