From: SeongJae Park <sj38.park@gmail.com>
To: byungchul.park@lge.com, paulmck@linux.vnet.ibm.com,
corbet@lwn.net, mingo@kernel.org
Cc: dhowells@redhat.com, minchan@kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH v5 1/2] Doc/memory-barriers: Fix a typo of example result
Date: Thu, 21 Jul 2016 10:10:57 +0900 [thread overview]
Message-ID: <1469063458-6573-2-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1469063458-6573-1-git-send-email-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>
---
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 19c8eb6..ba818ec 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
--
1.9.1
next prev parent reply other threads:[~2016-07-21 1:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 1:10 [PATCH v5 0/2] Doc/memory-barriers: Add Korean translation SeongJae Park
2016-07-21 1:10 ` SeongJae Park [this message]
2016-07-21 14:11 ` [PATCH v5 1/2] Doc/memory-barriers: Fix a typo of example result Paul E. McKenney
2016-07-21 1:10 ` [PATCH v5 2/2] Doc/memory-barriers: Add Korean translation SeongJae Park
2016-07-21 14:23 ` Paul E. McKenney
2016-07-21 14:54 ` SeongJae Park
2016-07-21 14:56 ` [PATCH] " SeongJae Park
2016-07-21 16:20 ` Paul E. McKenney
2016-07-21 16:54 ` SeongJae Park
2016-07-21 16:56 ` SeongJae Park
2016-07-21 17:26 ` Paul E. McKenney
2016-07-22 3:53 ` Byungchul Park
2016-07-22 4:01 ` SeongJae Park
2016-07-22 4:35 ` Byungchul Park
2016-07-22 4:03 ` Paul E. McKenney
2016-07-21 15:20 ` [PATCH v5 2/2] " Jonathan Corbet
2016-07-21 16:15 ` Ingo Molnar
2016-07-21 16:20 ` 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=1469063458-6573-2-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=byungchul.park@lge.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.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
Powered by JetHome