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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 12 Aug 2016 01:25:46 -0700
From:	tip-bot for SeongJae Park <tipbot@...or.com>
To:	linux-tip-commits@...r.kernel.org
Cc:	hpa@...or.com, mingo@...nel.org, linux-kernel@...r.kernel.org,
	sj38.park@...il.com, tglx@...utronix.de,
	torvalds@...ux-foundation.org, paulmck@...ux.vnet.ibm.com,
	peterz@...radead.org
Subject: [tip:locking/core] locking/Documentation: Fix wrong section
 reference

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

locking/Documentation: Fix wrong section reference

Signed-off-by: SeongJae Park <sj38.park@...il.com>
Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: dhowells@...hat.com
Cc: linux-arch@...r.kernel.org
Cc: will.deacon@....com
Link: http://lkml.kernel.org/r/1470939463-31950-2-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@...nel.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: