hm, I still get the falsie when checking this very patch.
Link:
http://lkml.kernel.org/r/eda977eaa8328fef42bb3c87935d9...@perches.com
Signed-off-by: Joe Perches <
j...@perches.com>
Reported-by: Andrew Morton <
ak...@linux-foundation.org>
Signed-off-by: Andrew Morton <
ak...@linux-foundation.org>
diff -puN scripts/
checkpatch.pl~checkpatch-reduce-git-commit-description-style-false-positives scripts/
checkpatch.pl
--- a/scripts/
checkpatch.pl~checkpatch-reduce-git-commit-description-style-false-positives
+++ a/scripts/
checkpatch.pl
@@ -2454,6 +2454,7 @@ sub process {
# Check for git id commit length and improperly formed commit descriptions
if ($in_commit_log && !$commit_log_possible_stack_dump &&
+ $line !~ /^\s*(?:Link|Patchwork|http|BugLink):/i &&
($line =~ /\bcommit\s+[0-9a-f]{5,}\b/i ||
($line =~ /\b[0-9a-f]{12,40}\b/i &&
$line !~ /[\<\[][0-9a-f]{12,40}[\>\]]/i &&
_
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#6:
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
Perhaps we could special-case the "unwrapped commit description" as
well - the Link: lines are almost always too wide.