The patch titled
checkpatch.pl: warn if an adding line introduce spaces before tabs.
has been added to the -mm tree. Its filename is
checkpatchpl-warn-if-an-adding-line-introduce-spaces-before-tabs.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: checkpatch.pl: warn if an adding line introduce spaces before tabs.
From: Alberto Panizzo <maramaopercheseimorto@xxxxxxxxx>
Signed-off-by: Alberto Panizzo <maramaopercheseimorto@xxxxxxxxx>
Cc: Andy Whitcroft <apw@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
scripts/checkpatch.pl | 6 ++++++
1 file changed, 6 insertions(+)
diff -puN scripts/checkpatch.pl~checkpatchpl-warn-if-an-adding-line-introduce-spaces-before-tabs scripts/checkpatch.pl
--- a/scripts/checkpatch.pl~checkpatchpl-warn-if-an-adding-line-introduce-spaces-before-tabs
+++ a/scripts/checkpatch.pl
@@ -1422,6 +1422,12 @@ sub process {
ERROR("code indent should use tabs where possible\n" . $herevet);
}
+# check for space before tabs.
+ if ($rawline =~ /^\+/ && $rawline =~ / \t/) {
+ my $herevet = "$here\n" . cat_vet($rawline) . "\n";
+ WARN("please, no space before tabs\n" . $herevet);
+ }
+
# check we are in a valid C source file if not then ignore this hunk
next if ($realfile !~ /\.(h|c)$/);
_
Patches currently in -mm which might be from maramaopercheseimorto@xxxxxxxxx are
linux-next.patch
mx3fb-some-debug-and-initialisation-fixes.patch
checkpatchpl-warn-if-an-adding-line-introduce-spaces-before-tabs.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
