From: Nachiket Naganure <nachiketun8@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: apw@canonical.com, lukas.bulwahn@gmail.com,
skhan@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] checkpatch: disable commit log length check warning for signature tag
Date: Mon, 27 Jul 2020 12:41:59 +0530 [thread overview]
Message-ID: <20200727071159.GA595854@endurance> (raw)
In-Reply-To: <66bbaec73d8f69541535db5390c0f12b304c0467.camel@perches.com>
On Sun, Jul 26, 2020 at 11:14:42PM -0700, Joe Perches wrote:
> On Mon, 2020-07-27 at 11:24 +0530, Nachiket Naganure wrote:
> > Disable commit log length check in case of signature tag. If the commit
> > log line has valid signature tags such as "Reported-and-tested-by" with
> > more than 75 characters, suppress the long length warning.
> >
> > For instance in commit ac854131d984 ("USB: core: Fix misleading driver bug
> > report"), the corresponding patch contains a "Reported by" tag line which
> > exceeds 75 chars. And there is no valid way to shorten the length.
> >
> > Signed-off-by: Nachiket Naganure <nachiketun8@gmail.com>
> > ---
> > scripts/checkpatch.pl | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 197436b20288..46237e9e0550 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -2806,6 +2806,8 @@ sub process {
> > # filename then :
> > $line =~ /^\s*(?:Fixes:|Link:)/i ||
> > # A Fixes: or Link: line
> > + $line =~ /$signature_tags/ ||
> > + # Check for signature_tags
> > $commit_log_possible_stack_dump)) {
> > WARN("COMMIT_LOG_LONG_LINE",
> > "Possible unwrapped commit description (prefer a maximum 75 chars per line)\n" . $herecurr);
>
> OK, but the test should be:
>
> $line =~ /^\s*$signature_tags/ ||
>
> so the line has to start with a signature and
> it won't match on signature tags in the middle
> of other content on the same line.
>
>
But the suggested won't work in case of merged signatures.
Such as "Reported-and-tested-by: user@email.com"
next prev parent reply other threads:[~2020-07-27 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 5:54 [PATCH] checkpatch: disable commit log length check warning for signature tag Nachiket Naganure
2020-07-27 6:14 ` Joe Perches
2020-07-27 7:11 ` Nachiket Naganure [this message]
2020-07-27 20:34 ` Lukas Bulwahn
2020-07-27 21:17 ` Joe Perches
2020-07-28 4:46 ` Nachiket Naganure
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=20200727071159.GA595854@endurance \
--to=nachiketun8@gmail.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=skhan@linuxfoundation.org \
/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