From: Oleg Nesterov <oleg@tv-sign.ru>
Date: Thu, 9 Nov 2006 01:44:38 +0000 (-0800)
Subject: [PATCH] A minor fix for set_mb() in Documentation/memory-barriers.txt
X-Git-Tag: v2.6.19-rc6~66
X-Git-Url: http://pilppa.com/gitweb/?a=commitdiff_plain;h=75b2bd55bd7724c727856fbdf3ab71d2e4287ac8;p=linux-2.6-omap-h63xx.git

[PATCH] A minor fix for set_mb() in Documentation/memory-barriers.txt

set_mb() is used by set_current_state() which needs mb(), not wmb().  I
think it would be right to assume that set_mb() implies mb(), all arches
seem to do just this.

Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Acked-by: David Howells <dhowells@redhat.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
---

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 7f790f66ec6..7751704b6db 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1016,7 +1016,7 @@ There are some more advanced barrier functions:
 
  (*) set_mb(var, value)
 
-     This assigns the value to the variable and then inserts at least a write
+     This assigns the value to the variable and then inserts a full memory
      barrier after it, depending on the function.  It isn't guaranteed to
      insert anything more than a compiler barrier in a UP compilation.