From: Derek Chickles <dchickles@caviumnetworks.com>
To: <joe@perches.com>
Cc: <apw@canonical.com>, <computersforpeace@gmail.com>,
<linux-kernel@vger.kernel.org>, <cernekee@gmail.com>,
Derek Chickles <dchickles@caviumnetworks.com>,
Derek Chickles <derek.chickles@caviumnetworks.com>
Subject: [PATCH] checkpatch: Fix MAINTAINERS search pattern
Date: Thu, 18 Dec 2014 12:12:13 -0800 [thread overview]
Message-ID: <1418933533-8364-1-git-send-email-dchickles@caviumnetworks.com> (raw)
In-Reply-To: <1418801732-19141-1-git-send-email-computersforpeace@gmail.com>
This fixes the check that was supposed to prevent the MAINTAINERS
warning from appearing when you run checkpatch.pl on a patch that
includes new files/directories and an updated MAINTAINERS file.
Signed-off-by: Derek Chickles <derek.chickles@caviumnetworks.com>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index f0bb6d6..6f10ebb 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2085,7 +2085,7 @@ sub process {
# Check if MAINTAINERS is being updated. If so, there's probably no need to
# emit the "does MAINTAINERS need updating?" message on file add/move/delete
- if ($line =~ /^\s*MAINTAINERS\s*\|/) {
+ if ($realfile =~ /MAINTAINERS/) {
$reported_maintainer_file = 1;
}
--
1.8.3.1
next prev parent reply other threads:[~2014-12-18 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 7:35 [PATCH] checkpatch: enable MAINTAINERS warning only for --strict,--subjective Brian Norris
2014-12-17 9:27 ` Joe Perches
2014-12-17 15:53 ` Kevin Cernekee
2014-12-17 17:26 ` Joe Perches
2014-12-18 20:12 ` Derek Chickles [this message]
2014-12-18 21:17 ` [PATCH] checkpatch: Fix MAINTAINERS search pattern Joe Perches
2014-12-19 2:34 ` Chickles, Derek
2014-12-19 3:57 ` 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=1418933533-8364-1-git-send-email-dchickles@caviumnetworks.com \
--to=dchickles@caviumnetworks.com \
--cc=apw@canonical.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=derek.chickles@caviumnetworks.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®