From: Scott Branden <scott.branden@broadcom.com>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: add check for NONNETWORKING_BLOCK_COMMENT_STYLE
Date: Wed, 10 Jun 2020 14:33:14 -0700 [thread overview]
Message-ID: <021da2ca-a8d3-d0ad-28c3-6a84464353fd@broadcom.com> (raw)
In-Reply-To: <673c2ebaf7a1ca93f3b1192a77ff62167badd896.camel@perches.com>
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.
But, by adding to checkpatch the coding style clearly outlined in
coding-style.rst can be followed:
The preferred style for long (multi-line) comments is:
.. code-block:: c
/*
* This is the preferred style for multi-line
* comments in the Linux kernel source code.
* Please use it consistently.
*
* Description: A column of asterisks on the left side,
* with beginning and ending almost-blank lines.
*/
For files in net/ and drivers/net/ the preferred style for long (multi-line)
comments is a little different.
.. code-block:: c
/* The preferred comment style for files in net/ and drivers/net
* looks like this.
*
* It is nearly the same as the generally preferred comment style,
* but there is no initial almost-blank line.
*/
>
> (with a few false positives)
>
> Does anyone really care if non-network code uses
> this style?
Yes we do.
Consistent coding style is great and keeps your brain able to focus on
what matters when it is consistent.
>
> /* multiline
> * comment
> */
>
>> 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);
>> + }
>> +
>> # Block comments use * on subsequent lines
>> if ($prevline =~ /$;[ \t]*$/ && #ends in comment
>> $prevrawline =~ /^\+.*?\/\*/ && #starting /*
next prev parent reply other threads:[~2020-06-10 21:33 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 [this message]
2020-06-10 21:42 ` Joe Perches
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=021da2ca-a8d3-d0ad-28c3-6a84464353fd@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=apw@canonical.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®