From: Scott Tsai <scottt@scottt.tw>
Date: Tue, 19 Sep 2017 18:16:00 +0000 (+0800)
Subject: memory-barriers.txt: Fix typo in pairing example
X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=d92f842bb30f52beedad63a4a850b39ca0dbc45f;p=linux.git

memory-barriers.txt: Fix typo in pairing example

In the "general barrier pairing with implicit control depdendency"
example, the last write by CPU 1 was meant to change variable x and not
y. The example would be pretty uninteresting if no CPU ever changes x
and the variable was initialized to zero.

Signed-off-by: Scott Tsai <scottt@scottt.tw>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 7deee14416406..f37375544d71d 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -947,7 +947,7 @@ Or even:
 	===============	      ===============================
 	r1 = READ_ONCE(y);
 	<general barrier>
-	WRITE_ONCE(y, 1);     if (r2 = READ_ONCE(x)) {
+	WRITE_ONCE(x, 1);     if (r2 = READ_ONCE(x)) {
 			         <implicit control dependency>
 			         WRITE_ONCE(y, 1);
 			      }