From: Joe Perches <joe@perches.com>
To: Scott Branden <scott.branden@broadcom.com>,
Andy Whitcroft <apw@canonical.com>
Cc: BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch: add check for NONNETWORKING_BLOCK_COMMENT_STYLE
Date: Wed, 10 Jun 2020 14:42:51 -0700 [thread overview]
Message-ID: <33204a397b2d9316e09ae9829e637894b304ea00.camel@perches.com> (raw)
In-Reply-To: <021da2ca-a8d3-d0ad-28c3-6a84464353fd@broadcom.com>
On Wed, 2020-06-10 at 14:33 -0700, Scott Branden wrote:
> Hi Joe,
>
> On 2020-06-10 2:16 p.m., Joe Perches wrote:
> > On Wed, 2020-06-10 at 13:26 -0700, Scott Branden wrote:
> > > NETWORKING_BLOCK_COMMENT_STYLE is supported by checkpatch but there
> > > doesn't seem to be any check for the standard block comment style.
> > > Add support for NONNETWORKING_BLOCK_COMMENT_STYLE to check for empty /*
> > > on first line of non-networking block comments.
> > I think there are _way_ too many instances of this form
> > in non-networking code to enable this.
> >
> > $ git grep -P '^\s*/\*\s*\S.*[^\*][^\\]\s*$' -- '*.[ch]' | \
> > grep -v -P '^(drivers/net/|net/)' | \
> > wc -l
> > 51407
> That is true about many things that checkpatch now checks for that
> didn't previously.
Not in that quantity of uses it doesn't.
I specifically did _not_ add this very same test
when I added the other comment tests.
> But, by adding to checkpatch the coding style clearly outlined in
> coding-style.rst can be followed:
Well, because there are _so_ many false positives
that don't need change, I'm not adding this.
As is, I'm nacking it.
If you need it for your use, you should keep it in
your own tree.
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > []
> > > @@ -3408,6 +3408,16 @@ sub process {
> > > "networking block comments don't use an empty /* line, use /* Comment...\n" . $hereprev);
> > > }
> > >
> > > +# Non-Networking with an empty initial /*
> > > + if ($realfile !~ m@^(drivers/net/|net/)@ &&
> > > + $prevrawline =~ /^\+[ \t]*\/\*[ \t]/ &&
> > > + $prevrawline !~ /\*\/[ \t]*$/ && #no trailing */
> > > + $rawline =~ /^\+[ \t]*\*/ &&
> > > + $realline > 2) {
> > > + WARN("NONNETWORKING_BLOCK_COMMENT_STYLE",
> > > + "non-networking block comments use an empty /* on first line\n" . $hereprev);
_Maybe_ this test _might_ be useful if it did a file/patch
test and used CHK on file, but even then I'm very dubious.
my $msg_level = \&WARN;
$msg_level = \&CHK if ($file);
&{msg_level}(etc...)
next prev parent reply other threads:[~2020-06-10 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 20:26 Scott Branden
2020-06-10 21:16 ` Joe Perches
2020-06-10 21:33 ` Scott Branden
2020-06-10 21:42 ` Joe Perches [this message]
2020-06-10 22:08 ` Scott Branden
2020-06-10 22:41 ` Joe Perches
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=33204a397b2d9316e09ae9829e637894b304ea00.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.branden@broadcom.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®