summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRandy Dunlap <randy.dunlap@oracle.com>2008-10-15 22:01:59 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-10-16 11:21:32 -0700
commit8033fe65a6d6c0e47ba9e3cb2e4e6902f9dfb8dd (patch)
tree5f1531ef9cd4bc0f3056ff904696437652685f07
parent7968b3d9a673e922ab980b2616945e63a52d88fe (diff)
downloadlinux-8033fe65a6d6c0e47ba9e3cb2e4e6902f9dfb8dd.tar.bz2
documentation: explain memory barriers
We want all uses of memory barriers to be explained in the source code. Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--Documentation/SubmitChecklist3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/SubmitChecklist b/Documentation/SubmitChecklist
index 21f0795af20f..ac5e0b2f1097 100644
--- a/Documentation/SubmitChecklist
+++ b/Documentation/SubmitChecklist
@@ -85,3 +85,6 @@ kernel patches.
23: Tested after it has been merged into the -mm patchset to make sure
that it still works with all of the other queued patches and various
changes in the VM, VFS, and other subsystems.
+
+24: All memory barriers {e.g., barrier(), rmb(), wmb()} need a comment in the
+ source code that explains the logic of what they are doing and why.