The patch titled
documentation: explain memory barriers
has been removed from the -mm tree. Its filename was
documentation-explain-memory-barriers.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: documentation: explain memory barriers
From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
We want all uses of memory barriers to be explained in the source code.
Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/SubmitChecklist | 3 +++
1 file changed, 3 insertions(+)
diff -puN Documentation/SubmitChecklist~documentation-explain-memory-barriers Documentation/SubmitChecklist
--- a/Documentation/SubmitChecklist~documentation-explain-memory-barriers
+++ a/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.
_
Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are
origin.patch
memory_probe-fix-wrong-sysfs-file-attribute.patch
memory_probe-fix-wrong-sysfs-file-attribute-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
