X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=Documentation%2Fvolatile-considered-harmful.txt;h=db0cb228d64aa4a80a4fe380be3e46439de810e6;hb=1383923d1985cef2bceb8128094fbe5e05de7435;hp=991c26a6ef64fcfdef0fc870d3ed404f55751407;hpb=aef8755711a28bb0ecde7780ae6613fcb62cf6f7;p=deliverable%2Flinux.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: