linux-kernel - [PATCH] checkpatch: Fix MAINTAINERS search pattern

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1418933533-8364-1-git-send-email-dchickles@caviumnetworks.com>
Date:	Thu, 18 Dec 2014 12:12:13 -0800
From:	Derek Chickles <dchickles@...iumnetworks.com>
To:	<joe@...ches.com>
CC:	<apw@...onical.com>, <computersforpeace@...il.com>,
	<linux-kernel@...r.kernel.org>, <cernekee@...il.com>,
	Derek Chickles <dchickles@...iumnetworks.com>,
	Derek Chickles <derek.chickles@...iumnetworks.com>
Subject: [PATCH] checkpatch: Fix MAINTAINERS search pattern

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@...iumnetworks.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/