From: Aditya <yashsri421@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] checkpatch: fix false positive for COMMIT_LOG_LONG_LINE with URLs
Date: Wed, 16 Dec 2020 18:24:44 +0530 [thread overview]
Message-ID: <53238abd-2fdc-e9fb-bef5-4b583ccb14e2@gmail.com> (raw)
In-Reply-To: <CAKXUXMx+Jogibwf_WbC7RQ0jD2+uU=XvpF4JxSWtz+3C_bRWSg@mail.gmail.com>
On 16/12/20 6:05 pm, Lukas Bulwahn wrote:
> On Wed, Dec 16, 2020 at 1:32 PM Aditya Srivastava <yashsri421@gmail.com> wrote:
>>
>> Currently checkpatch warns for long line in commit messages even for
>> URL lines.
>>
>> An evaluation over v4.13..v5.8 showed that out of ~11000 warnings for
>> this class, around 790 are due to the line containing link.
>>
>> E.g. running checkpatch on commit 3cde818cd02b ("ASoC: topology:
>> Consolidate how dtexts and dvalues are freed") reports this warning:
>>
>> WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
>> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-January/144761.html
>>
>> Avoid giving users warning for character limit, instead suggest them to
>> prefix the URLs with "Link:"
>>
>
> Looks good to me. This might be also a good one for a fix option.
>
I agree. Should I add the fix in this patch itself?
Thanks
Aditya
> Lukas
>
>> Signed-off-by: Aditya Srivastava <yashsri421@gmail.com>
>> ---
>> scripts/checkpatch.pl | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index abd5a3d2e913..23da1f50fe6a 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -3032,8 +3032,14 @@ sub process {
>> $line =~ /^\s*(?:Fixes:|Link:|$signature_tags)/i ||
>> # A Fixes: or Link: line or signature tag line
>> $commit_log_possible_stack_dump)) {
>> - WARN("COMMIT_LOG_LONG_LINE",
>> - "Possible unwrapped commit description (prefer a maximum 75 chars per line)\n" . $herecurr);
>> + if ($line =~ /(?:http|https|ftp):\/\//) {
>> + WARN("COMMIT_LOG_LONG_LINE",
>> + "Consider prefixing the URL with 'Link:'\n" . $herecurr);
>> + }
>> + else {
>> + WARN("COMMIT_LOG_LONG_LINE",
>> + "Possible unwrapped commit description (prefer a maximum 75 chars per line)\n" . $herecurr);
>> + }
>> $commit_log_long_line = 1;
>> }
>>
>> --
>> 2.17.1
>>
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-12-16 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 12:31 [Linux-kernel-mentees] [PATCH] checkpatch: fix false positive for COMMIT_LOG_LONG_LINE with URLs Aditya Srivastava
2020-12-16 12:35 ` Lukas Bulwahn
2020-12-16 12:54 ` Aditya [this message]
2020-12-16 12:57 ` Lukas Bulwahn
2020-12-16 16:29 ` Aditya
2020-12-17 11:11 ` Aditya
2020-12-17 12:42 ` Lukas Bulwahn
-- strict thread matches above, loose matches on Subject: below --
2020-12-17 13:42 Aditya Srivastava
2020-12-17 17:03 ` Joe Perches
2020-12-17 19:35 ` Aditya
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=53238abd-2fdc-e9fb-bef5-4b583ccb14e2@gmail.com \
--to=yashsri421@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.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