Commit-ID: d7cab36db83be458e8987ae352902958977e7925 Gitweb: http://git.kernel.org/tip/d7cab36db83be458e8987ae352902958977e7925 Author: SeongJae Park <sj38.p...@gmail.com> AuthorDate: Thu, 11 Aug 2016 11:17:41 -0700 Committer: Ingo Molnar <mi...@kernel.org> CommitDate: Fri, 12 Aug 2016 08:24:13 +0200
locking/Documentation: Fix wrong section reference Signed-off-by: SeongJae Park <sj38.p...@gmail.com> Signed-off-by: Paul E. McKenney <paul...@linux.vnet.ibm.com> Cc: Linus Torvalds <torva...@linux-foundation.org> Cc: Peter Zijlstra <pet...@infradead.org> Cc: Thomas Gleixner <t...@linutronix.de> Cc: dhowe...@redhat.com Cc: linux-a...@vger.kernel.org Cc: will.dea...@arm.com Link: http://lkml.kernel.org/r/1470939463-31950-2-git-send-email-paul...@linux.vnet.ibm.com Signed-off-by: Ingo Molnar <mi...@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:
