X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=Documentation%2Fvolatile-considered-harmful.txt;h=db0cb228d64aa4a80a4fe380be3e46439de810e6;hb=841bcd2e5014f83ed99e88bd550645d8848ce19a;hp=991c26a6ef64fcfdef0fc870d3ed404f55751407;hpb=ce6754235b423610e91f5300e1555c2e4ee1c03a;p=karo-tx-linux.git

diff --git a/Documentation/volatile-considered-harmful.txt b/Documentation/volatile-considered-harmful.txt
index 991c26a6ef64..db0cb228d64a 100644
--- a/Documentation/volatile-considered-harmful.txt
+++ b/Documentation/volatile-considered-harmful.txt
@@ -63,9 +63,9 @@ way to perform a busy wait is:
         cpu_relax();
 
 The cpu_relax() call can lower CPU power consumption or yield to a
-hyperthreaded twin processor; it also happens to serve as a memory barrier,
-so, once again, volatile is unnecessary.  Of course, busy-waiting is
-generally an anti-social act to begin with.
+hyperthreaded twin processor; it also happens to serve as a compiler
+barrier, so, once again, volatile is unnecessary.  Of course, busy-
+waiting is generally an anti-social act to begin with.
 
 There are still a few rare situations where volatile makes sense in the
 kernel: