From: Randy Dunlap <randy.dunlap@oracle.com>
Date: Thu, 16 Oct 2008 05:01:59 +0000 (-0700)
Subject: documentation: explain memory barriers
X-Git-Tag: v2.6.28-rc1~517
X-Git-Url: http://pilppa.com/gitweb/?a=commitdiff_plain;h=8033fe65a6d6c0e47ba9e3cb2e4e6902f9dfb8dd;p=linux-2.6-omap-h63xx.git

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>
---

diff --git a/Documentation/SubmitChecklist b/Documentation/SubmitChecklist
index 21f0795af20..ac5e0b2f109 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.