In the description of data dependency barriers the words 'before' is
used erroneously. Since such barrier order dependent loads one after
the other. So substitute 'before' with 'after'.

Signed-off-by: Nikolay Borisov <>

Resent due to missing out the various mailing lists doh ... 

 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt 
index a863009849a3..0d696c7fd97a 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
      where two loads are performed such that the second depends on the result
      of the first (eg: the first load retrieves the address to which the second
      load will be directed), a data dependency barrier would be required to
-     make sure that the target of the second load is updated before the address
+     make sure that the target of the second load is updated after the address
      obtained by the first load is accessed.
      A data dependency barrier is a partial ordering on interdependent loads

To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to
More majordomo info at

Reply via email to