mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Andy Whitcroft <apw@canonical.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Checking for space before ending comment tag
Date: Sat, 19 Mar 2022 01:42:20 -0700	[thread overview]
Message-ID: <b42be7ee3ed3a2356b7c5ddad545e12d5e7a0ee7.camel@perches.com> (raw)
In-Reply-To: <fb2ab099-aefa-6a84-5c62-f0c87eca2725@molgen.mpg.de>

On Sat, 2022-03-19 at 08:35 +0100, Paul Menzel wrote:
> Dear Andy, dear Joe,
> 
> The attached patch misses a space before the closing comment tag `*/`:
> 
>      /* Check for FEC status*/
> 
>      $ git describe origin/master
>      v5.17-rc8-61-g34e047aa16c0
>      $ scripts/checkpatch.pl 
> /dev/shm/0001-drm-amd-display-FEC-check-in-timing-validation.patch
>      total: 0 errors, 0 warnings, 10 lines checked
> 
>      /dev/shm/0001-drm-amd-display-FEC-check-in-timing-validation.patch 
> has no obvious style problems and is ready for submission.
> 
> Should/could checkpatch.pl warn about that?

It _could_, but there are a large number of existing uses in the kernel.

$ git grep -P '\w\*\/\s*$' -- '*.[ch]' | wc -l
15841

Even when you exclude the uses that start with /*\w

$ git grep -P '\w\*\/\s*$' -- '*.[ch]' | grep -v -P '/\*\w' | wc -l
7239

btw: that doesn't count the thousands of lines like

/*----*/

Anyway, I prefer not to add tests for things that have that many uses.

cheers, Joe

Anyway, maybe a test could be something like:
---
 scripts/checkpatch.pl | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 577e029987011..65800e6964d1e 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3868,6 +3868,14 @@ sub process {
 			}
 		}
 
+# Single line comment style
+		if ($line =~ /^\+.*$;\s*$/ &&
+		    $rawline =~ /\/\* / &&
+		    $rawline =~ /\w\*\/\s*$/) {
+			WARN("COMMENT_STYLE",
+			     "Single line comments should use a space before the comment termination\n" . $herecurr);
+		}
+
 # Block comment styles
 # Networking with an initial /*
 		if ($realfile =~ m@^(drivers/net/|net/)@ &&



       reply	other threads:[~2022-03-19  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fb2ab099-aefa-6a84-5c62-f0c87eca2725@molgen.mpg.de>
2022-03-19  8:42 ` Joe Perches [this message]
2022-03-20  2:30   ` 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=b42be7ee3ed3a2356b7c5ddad545e12d5e7a0ee7.camel@perches.com \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    /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®