[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1423160064.4752.9.camel@perches.com>
Date: Thu, 05 Feb 2015 10:14:24 -0800
From: Joe Perches <joe@...ches.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Andy Whitcroft <apw@...onical.com>,
Al Viro <viro@...IV.linux.org.uk>,
Dan Carpenter <dan.carpenter@...cle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH] checkpatch: Try to avoid poor patch subject lines
Naming the tool that found an issue in the subject line isn't
very useful. Emit a warning when a common tool (currently
checkpatch, sparse or smatch) is in the subject line.
Signed-off-by: Joe Perches <joe@...ches.com>
Inspired-by: Al Viro <viro@...IV.linux.org.uk>
Acked-by: Dan Carpenter <dan.carpenter@...cle.com>
Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
scripts/checkpatch.pl | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 3642b0d..b6bed59 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2170,6 +2170,13 @@ sub process {
}
}
+# Check email subject for common tools that don't need to be mentioned
+ if ($in_header_lines &&
+ $line =~ /^Subject:.*\b(?:checkpatch|sparse|smatch)\b[^:]/i) {
+ WARN("EMAIL_SUBJECT",
+ "A patch subject line should describe the change not the tool that found it\n" . $herecurr);
+ }
+
# Check for old stable address
if ($line =~ /^\s*cc:\s*.*<?\bstable\@kernel\.org\b>?.*$/i) {
ERROR("STABLE_ADDRESS",
--
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/
Powered by blists - more mailing lists