public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Srikanth Thokala <sriku.linux@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Srikanth Thokala <sriku.linux@gmail.com>
Subject: [PATCH] Documentation: memory-barriers: Fix typo in the first example
Date: Tue, 18 Nov 2014 10:09:58 +0530	[thread overview]
Message-ID: <1416285598-6630-1-git-send-email-sriku.linux@gmail.com> (raw)

In the first example, the loads into 'x' and 'y' on CPU 2 doesn't
match the sequence of events described below it.  To match the
sequence of events, the values of 'A' and 'B' should be loaded
into 'x' and 'y' respectively.

Signed-off-by: Srikanth Thokala <sriku.linux@gmail.com>
---
 Documentation/memory-barriers.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 22a969c..2770bce 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -115,8 +115,8 @@ For example, consider the following sequence of events:
 	CPU 1		CPU 2
 	===============	===============
 	{ A == 1; B == 2 }
-	A = 3;		x = B;
-	B = 4;		y = A;
+	A = 3;		x = A;
+	B = 4;		y = B;
 
 The set of accesses as seen by the memory system in the middle can be arranged
 in 24 different combinations:
-- 
1.9.1


             reply	other threads:[~2014-11-18  4:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  4:39 Srikanth Thokala [this message]
2014-11-27  6:49 ` [PATCH] Documentation: memory-barriers: Fix typo in the first example Srikanth Thokala
2014-12-02 21:15   ` Jonathan Corbet
2014-12-02 21:50     ` Paul E. McKenney
2014-12-02 22:01       ` Jonathan Corbet
2014-12-02 22:09         ` Paul E. McKenney
2014-12-03  0:15           ` Måns Rullgård
2014-12-03  0:27             ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1416285598-6630-1-git-send-email-sriku.linux@gmail.com \
    --to=sriku.linux@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox