From: tip-bot for SeongJae Park <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, mingo@kernel.org, linux-kernel@vger.kernel.org,
sj38.park@gmail.com, tglx@linutronix.de,
torvalds@linux-foundation.org, paulmck@linux.vnet.ibm.com,
peterz@infradead.org
Subject: [tip:locking/core] locking/Documentation: Fix wrong section reference
Date: Fri, 12 Aug 2016 01:25:46 -0700 [thread overview]
Message-ID: <tip-d7cab36db83be458e8987ae352902958977e7925@git.kernel.org> (raw)
In-Reply-To: <1470939463-31950-2-git-send-email-paulmck@linux.vnet.ibm.com>
Commit-ID: d7cab36db83be458e8987ae352902958977e7925
Gitweb: http://git.kernel.org/tip/d7cab36db83be458e8987ae352902958977e7925
Author: SeongJae Park <sj38.park@gmail.com>
AuthorDate: Thu, 11 Aug 2016 11:17:41 -0700
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 12 Aug 2016 08:24:13 +0200
locking/Documentation: Fix wrong section reference
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: dhowells@redhat.com
Cc: linux-arch@vger.kernel.org
Cc: will.deacon@arm.com
Link: http://lkml.kernel.org/r/1470939463-31950-2-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
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 e1926a0..19c8eb6 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -2076,7 +2076,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:
next prev parent reply other threads:[~2016-08-12 8:26 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-bot for SeongJae Park [this message]
2016-08-11 18:17 ` [PATCH memory-barriers.txt 3/4] Doc/memory-barriers: Fix a typo of example result Paul E. McKenney
2016-08-12 8:26 ` [tip:locking/core] locking/Documentation: " 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=tip-d7cab36db83be458e8987ae352902958977e7925@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sj38.park@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.