Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

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

Browse source 
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>
This commit is contained in:
Oleg Nesterov 2006-11-08 17:44:38 -08:00 committed by Linus Torvalds
parent d654c673d6
commit 75b2bd55bd
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Documentation/memory-barriers.txt
View file

@ -1016,7 +1016,7 @@ There are some more advanced barrier functions:
(*) set_mb(var, value) (*) 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 barrier after it, depending on the function. It isn't guaranteed to
insert anything more than a compiler barrier in a UP compilation. insert anything more than a compiler barrier in a UP compilation.