[tip:locking/core] locking/Documentation: Fix wrong section reference

From: tip-bot for SeongJae Park
Date: Fri Aug 12 2016 - 04:26:29 EST


Commit-ID: d7cab36db83be458e8987ae352902958977e7925
Gitweb: http://git.kernel.org/tip/d7cab36db83be458e8987ae352902958977e7925
Author: SeongJae Park <sj38.park@xxxxxxxxx>
AuthorDate: Thu, 11 Aug 2016 11:17:41 -0700
Committer: Ingo Molnar <mingo@xxxxxxxxxx>
CommitDate: Fri, 12 Aug 2016 08:24:13 +0200

locking/Documentation: Fix wrong section reference

Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
Signed-off-by: Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx>
Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Cc: dhowells@xxxxxxxxxx
Cc: linux-arch@xxxxxxxxxxxxxxx
Cc: will.deacon@xxxxxxx
Link: http://lkml.kernel.org/r/1470939463-31950-2-git-send-email-paulmck@xxxxxxxxxxxxxxxxxx
Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx>
---
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: