linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, peterz@infradead.org, dhowells@redhat.com,
	will.deacon@arm.com, linux-arch@vger.kernel.org,
	sj38.park@gmail.com,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH memory-barriers.txt 3/4] Doc/memory-barriers: Fix a typo of example result
Date: Thu, 11 Aug 2016 11:17:42 -0700	[thread overview]
Message-ID: <1470939463-31950-3-git-send-email-paulmck@linux.vnet.ibm.com> (raw)
In-Reply-To: <1470939463-31950-1-git-send-email-paulmck@linux.vnet.ibm.com>

From: SeongJae Park <sj38.park@gmail.com>

An example result for data dependent write has a typo.  This commit
fixes the wrong typo.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 19c8eb6f246e..ba818ecce6f9 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -609,7 +609,7 @@ A data-dependency barrier must also order against dependent writes:
 The data-dependency barrier must order the read into Q with the store
 into *Q.  This prohibits this outcome:
 
-	(Q == B) && (B == 4)
+	(Q == &B) && (B == 4)
 
 Please note that this pattern should be rare.  After all, the whole point
 of dependency ordering is to -prevent- writes to the data structure, along
-- 
2.5.2

  parent reply	other threads:[~2016-08-11 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 18:16 [PATCH memory-barriers.txt v2 0/5] Fixes and Korean translation Paul E. McKenney
2016-08-11 18:17 ` [PATCH memory-barriers.txt 1/4] memory-barriers.txt: Maintain consistent blank line Paul E. McKenney
2016-08-11 18:17   ` [PATCH memory-barriers.txt 2/4] memory-barriers.txt: Fix wrong section reference Paul E. McKenney
2016-08-12  8:25     ` [tip:locking/core] locking/Documentation: " tip-bot for SeongJae Park
2016-08-11 18:17   ` Paul E. McKenney [this message]
2016-08-12  8:26     ` [tip:locking/core] locking/Documentation: Fix a typo of example result tip-bot for SeongJae Park
2016-08-11 18:17   ` [PATCH memory-barriers.txt 4/4] Doc/memory-barriers: Add Korean translation Paul E. McKenney
2016-08-12  8:26     ` [tip:locking/core] locking/Documentation: " tip-bot for SeongJae Park
2016-08-12  8:25   ` [tip:locking/core] locking/Documentation: Maintain consistent blank line tip-bot for SeongJae Park

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=1470939463-31950-3-git-send-email-paulmck@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sj38.park@gmail.com \
    --cc=will.deacon@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).