Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] checkpatch: Allow consecutive close braces
Date: Tue, 27 Aug 2019 13:49:09 -0700	[thread overview]
Message-ID: <bfdb49ae2c3fa7b52fa168769e38b48f959880e2.camel@perches.com> (raw)
In-Reply-To: <c2279a78904b581924894b712403299903eacbfc.camel@intel.com>

checkpatch allows consecutive open braces, so it
should also allow consecutive close braces.

Signed-off-by: Joe Perches <joe@perches.com>
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 287fe73688f0..ac5e0f06e1af 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -4687,7 +4687,7 @@ sub process {
 
 # closing brace should have a space following it when it has anything
 # on the line
-		if ($line =~ /}(?!(?:,|;|\)))\S/) {
+		if ($line =~ /}(?!(?:,|;|\)|\}))\S/) {
 			if (ERROR("SPACING",
 				  "space required after that close brace '}'\n" . $herecurr) &&
 			    $fix) {



      parent reply	other threads:[~2019-08-27 20:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 19:14 [Intel-wired-lan] [PATCH] net: intel: Cleanup e1000 - add space between }} Forrest Fleming
2019-08-26  8:03 ` Jeff Kirsher
2019-08-27  3:41   ` Joe Perches
2019-08-27 19:02     ` Jeff Kirsher
2019-08-27 19:07       ` Joe Perches
2019-08-27 19:45         ` Forrest Fleming
2019-08-27 20:27           ` Jeff Kirsher
2019-08-27 20:27     ` Jeff Kirsher
2019-08-27 20:49   ` Joe Perches [this message]

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=bfdb49ae2c3fa7b52fa168769e38b48f959880e2.camel@perches.com \
    --to=joe@perches.com \
    --cc=intel-wired-lan@osuosl.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