From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com,
yashsri421@gmail.com
Subject: Re: [PATCH] checkpatch: improve handling of email comments
Date: Fri, 30 Oct 2020 12:58:47 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2010301255460.16621@felia> (raw)
In-Reply-To: <9d5c8699f94481ab5bf2d37348199ca1d6343c8b.camel@perches.com>
On Fri, 30 Oct 2020, Joe Perches wrote:
> On Fri, 2020-10-30 at 14:37 +0530, Dwaipayan Ray wrote:
> > checkpatch has limited support for parsing email comments. It only
> > support single name comments or single after address comments.
> > Whereas, RFC 5322 specifies that comments can be inserted in
> > between any tokens of the email fields.
> >
> > Improve comment parsing mechanism in checkpatch.
> >
> > What is handled now:
> >
> > - Multiple name/address comments
> > - Comments anywhere in between name/address
> > - Nested comments like (John (Doe))
> >
> > A brief analysis of checkpatch output on v5.0..v5.7 showed that
> > after these modifications, the number of BAD_SIGN_OFF warnings
> > came down from 2944 to 1424, and FROM_SIGN_OFF_MISMATCH came
> > down from 2366 to 2330.
> >
> > So, a total of 1556 false positives were resolved in total.
>
> A mere reduction in messages emitted isn't necessarily good.
>
Agree. That is why I also went through the list of those warnings.
I could not spot any obvious true positive among the reduced ones.
> Please send me privately a complete list of these nominally
> false positive messages that are no longer emitted.
>
> I believe one of the relatively common incorrect messages is
> for the cc: <stable@vger.kernel.org> where a version number is
> continued on the same line after a #.
>
> CC: stable@vger.kernel.org # for versions x.y.z and above
>
That was one, another common pattern was just quotes put inconsistently at
different places.
Lukas
next prev parent reply other threads:[~2020-10-30 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 9:07 Dwaipayan Ray
2020-10-30 11:54 ` Joe Perches
2020-10-30 11:58 ` Lukas Bulwahn [this message]
2020-10-30 12:21 ` Joe Perches
2020-10-31 4:14 ` Joe Perches
2020-10-31 6:11 ` Dwaipayan Ray
2020-10-31 11:14 ` Joe Perches
2020-10-31 21:08 ` 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=alpine.DEB.2.21.2010301255460.16621@felia \
--to=lukas.bulwahn@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yashsri421@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®