From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: dhowells@redhat.com, corbet@lwn.net, minchan@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 3/5] doc/memory-barriers: fix typo
Date: Thu, 10 Mar 2016 09:48:57 +0900 [thread overview]
Message-ID: <1457570939-7740-4-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1457570939-7740-1-git-send-email-sj38.park@gmail.com>
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
Documentation/memory-barriers.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 0560a49..89f96af 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -149,7 +149,7 @@ As a further example, consider this sequence of events:
CPU 1 CPU 2
=============== ===============
- { A == 1, B == 2, C = 3, P == &A, Q == &C }
+ { A == 1, B == 2, C == 3, P == &A, Q == &C }
B = 4; Q = P;
P = &B D = *Q;
@@ -518,7 +518,7 @@ following sequence of events:
CPU 1 CPU 2
=============== ===============
- { A == 1, B == 2, C = 3, P == &A, Q == &C }
+ { A == 1, B == 2, C == 3, P == &A, Q == &C }
B = 4;
<write barrier>
WRITE_ONCE(P, &B)
@@ -545,7 +545,7 @@ between the address load and the data load:
CPU 1 CPU 2
=============== ===============
- { A == 1, B == 2, C = 3, P == &A, Q == &C }
+ { A == 1, B == 2, C == 3, P == &A, Q == &C }
B = 4;
<write barrier>
WRITE_ONCE(P, &B);
@@ -3042,7 +3042,7 @@ The Alpha defines the Linux kernel's memory barrier model.
See the subsection on "Cache Coherency" above.
VIRTUAL MACHINE GUESTS
--------------------
+----------------------
Guests running within virtual machines might be affected by SMP effects even if
the guest itself is compiled without SMP support. This is an artifact of
--
1.9.1
next prev parent reply other threads:[~2016-03-10 0:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 0:48 [PATCH 0/5] Add Korean translation of memory-barriers.txt SeongJae Park
2016-03-10 0:48 ` [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire SeongJae Park
2016-03-10 0:48 ` [PATCH 2/5] doc/memory-barriers: add missed subsection in TOC SeongJae Park
2016-03-10 0:48 ` SeongJae Park [this message]
2016-03-10 0:48 ` [PATCH 4/5] doc/memory-barriers: Insert white spaces consistently SeongJae Park
2016-03-10 0:48 ` [PATCH 5/5] Doc/memory-barriers: add Korean translation SeongJae Park
2016-03-10 2:01 ` [PATCH 0/5] Add Korean translation of memory-barriers.txt Paul E. McKenney
2016-03-10 8:13 ` [PATCH 1/5] doc/memory-barriers: fix missed renaming: s/lock/acquire David Howells
2016-03-10 8:50 ` SeongJae Park
2016-03-10 9:45 ` David Howells
2016-03-10 14:39 ` SeongJae Park
2016-03-10 8:14 ` [PATCH 4/5] doc/memory-barriers: Insert white spaces consistently David Howells
2016-03-10 8:15 ` [PATCH 3/5] doc/memory-barriers: fix typo David Howells
2016-03-10 8:16 ` [PATCH 2/5] doc/memory-barriers: add missed subsection in TOC David Howells
2016-03-10 8:17 ` [PATCH 5/5] Doc/memory-barriers: add Korean translation David Howells
2016-03-11 8:56 ` [PATCH 0/5] Add Korean translation of memory-barriers.txt Gioh Kim
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=1457570939-7740-4-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.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=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;
as well as URLs for NNTP newsgroup(s).