From: SeongJae Park <sj38.park@gmail.com>
To: byungchul.park@lge.com, paulmck@linux.vnet.ibm.com
Cc: dhowells@redhat.com, minchan@kernel.org, mingo@kernel.org,
corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH v4 2/3] memory-barriers.txt: fix wrong section reference
Date: Mon, 4 Jul 2016 08:27:07 +0900 [thread overview]
Message-ID: <1467588428-5838-3-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1467588428-5838-1-git-send-email-sj38.park@gmail.com>
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 360faf4..5af1139 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -2035,7 +2035,7 @@ systems, and so cannot be counted on in such a situation to actually achieve
anything at all - especially with respect to I/O accesses - unless combined
with interrupt disabling operations.
-See also the section on "Inter-CPU locking barrier effects".
+See also the section on "Inter-CPU acquiring barrier effects".
As an example, consider the following:
--
1.9.1
next prev parent reply other threads:[~2016-07-03 23:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 23:27 [PATCH v4 0/3] Doc/memory-barriers: Add Korean translation SeongJae Park
2016-07-03 23:27 ` [PATCH v4 1/3] memory-barriers.txt: maintain consistent blank line SeongJae Park
2016-07-03 23:27 ` SeongJae Park [this message]
2016-07-03 23:27 ` [PATCH v4 3/3] Doc/memory-barriers: Add Korean translation SeongJae Park
2016-07-05 12:34 ` Byungchul Park
2016-07-05 21:57 ` SeongJae Park
2016-07-07 12:00 ` Byungchul Park
2016-07-07 22:50 ` SeongJae Park
2016-07-08 1:17 ` Byungchul Park
2016-07-08 10:13 ` Ingo Molnar
2016-07-08 10:22 ` SeongJae Park
2016-07-05 21:36 ` [PATCH v4 0/3] " Paul E. McKenney
2016-07-05 22:11 ` 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=1467588428-5838-3-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;
as well as URLs for NNTP newsgroup(s).