linux-kernel - [PATCH v4 2/3] memory-barriers.txt: 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:	Mon,  4 Jul 2016 08:27:07 +0900
From:	SeongJae Park <sj38.park@...il.com>
To:	byungchul.park@....com, paulmck@...ux.vnet.ibm.com
Cc:	dhowells@...hat.com, minchan@...nel.org, mingo@...nel.org,
	corbet@....net, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, SeongJae Park <sj38.park@...il.com>
Subject: [PATCH v4 2/3] memory-barriers.txt: fix wrong section reference

Signed-off-by: SeongJae Park <sj38.park@...il.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