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>

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>
Randy Dunlap · Linus Torvalds
1 parent 7968b3d9a6
Showing 1 changed file with 3 additions and 0 deletions Side-by-side Diff
Documentation/SubmitChecklist
@@ -85,4 +85,7 @@
 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.
...	...	@@ -85,4 +85,7 @@
85	85	23: Tested after it has been merged into the -mm patchset to make sure
86	86	that it still works with all of the other queued patches and various
87	87	changes in the VM, VFS, and other subsystems.
	88	+
	89	+24: All memory barriers {e.g., barrier(), rmb(), wmb()} need a comment in the
	90	+ source code that explains the logic of what they are doing and why.