Skip to content

Commit c1fd7bb

Browse files
JoePerchestorvalds
authored andcommitted
checkpatch: make the memory barrier test noisier
Peter Zijlstra prefers that comments be required near uses of memory barriers. Change the message level for memory barrier uses from a --strict test only to a normal WARN so it's always emitted. This might produce false positives around insertions of memory barriers when a comment is outside the patch context block. And checkpatch is still stupid, it only looks for existence of any comment, not at the comment content. Signed-off-by: Joe Perches <joe@perches.com> Suggested-by: Peter Zijlstra <peterz@infradead.org> Acked-by: Peter Zijlstra <peterz@infradead.org> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Oliver Neukum <oliver@neukum.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
1 parent e970b88 commit c1fd7bb

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

scripts/checkpatch.pl

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3850,8 +3850,8 @@ sub process {
38503850
# check for memory barriers without a comment.
38513851
if ($line =~ /\b(mb|rmb|wmb|read_barrier_depends|smp_mb|smp_rmb|smp_wmb|smp_read_barrier_depends)\(/) {
38523852
if (!ctx_has_comment($first_line, $linenr)) {
3853-
CHK("MEMORY_BARRIER",
3854-
"memory barrier without comment\n" . $herecurr);
3853+
WARN("MEMORY_BARRIER",
3854+
"memory barrier without comment\n" . $herecurr);
38553855
}
38563856
}
38573857
# check of hardware specific defines

0 commit comments

Comments
 (0)