From: Joe Perches <joe@perches.com>
To: Mark Rutland <mark.rutland@arm.com>,
daniel.lezcano@linaro.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: marc.zyngier@arm.com, tglx@linutronix.de,
ard.biesheuvel@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] checkpatch: Allow DEFINE_PER_CPU definitions to exceed line length
Date: Mon, 16 Oct 2017 09:12:00 -0700 [thread overview]
Message-ID: <1508170320.6530.15.camel@perches.com> (raw)
In-Reply-To: <20171016152839.14964-3-mark.rutland@arm.com>
Some of the definitions are very long and can't be split
into multiple lines because ctags is limited.
Exempt these lines from the line length checks.
Signed-off-by: Joe Perches <joe@perches.com>
---
scripts/checkpatch.pl | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 2a8c6c3c1bdb..5fa0f5467d99 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2900,8 +2900,9 @@ sub process {
$line =~ /^\+\s*#\s*define\s+\w+\s+$String$/) {
$msg_type = "";
- # EFI_GUID is another special case
- } elsif ($line =~ /^\+.*\bEFI_GUID\s*\(/) {
+ # More special cases
+ } elsif ($line =~ /^\+.*\bEFI_GUID\s*\(/ ||
+ $line =~ /^\+\s*(?:\w+)?\s*DEFINE_PER_CPU/) {
$msg_type = "";
# Otherwise set the alternate message types
next prev parent reply other threads:[~2017-10-16 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:28 [GIT PULL] arch_timer updates for v4.15 Mark Rutland
2017-10-16 15:28 ` [PATCH 1/2] clocksource: arm_arch_timer: validate CNTFRQ after enabling frame Mark Rutland
2017-10-16 15:28 ` [PATCH 2/2] clocksource: arm_arch_timer: fix DEFINE_PER_CPU expansion Mark Rutland
2017-10-16 16:12 ` Joe Perches [this message]
2017-10-16 16:32 ` [PATCH] checkpatch: Allow DEFINE_PER_CPU definitions to exceed line length Mark Rutland
2017-10-17 18:16 ` [GIT PULL] arch_timer updates for v4.15 Daniel Lezcano
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=1508170320.6530.15.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.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
Powered by JetHome