diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2017-07-13 13:44:54 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-07-13 13:44:54 -0700 |
| commit | 954e6e03c61d233eae810f8da65270c224fe2fa4 (patch) | |
| tree | bed7e17c864e84eb28a5ae4fa1ee809f4c2de783 /Documentation/memory-barriers.txt | |
| parent | 80fc62380995b02492245a9971944e4713a5eb63 (diff) | |
| parent | 51e988f4092428e3d2c9f141fba9f86583bc82f3 (diff) | |
| download | linux-riscv-954e6e03c61d233eae810f8da65270c224fe2fa4.tar.gz linux-riscv-954e6e03c61d233eae810f8da65270c224fe2fa4.tar.bz2 linux-riscv-954e6e03c61d233eae810f8da65270c224fe2fa4.zip | |
Merge tag '4.13-fixes' of git://git.lwn.net/linux
Pull documentation fixes from Jonathan Corbet:
"A set of fixes for various warnings, including the one caused by the
removal of kernel/rcu/srcu.c. Also correct a stray pointer in
memory-barriers.txt"
* tag '4.13-fixes' of git://git.lwn.net/linux:
kokr/memory-barriers.txt: Fix obsolete link to atomic_ops.txt
memory-barriers.txt: Fix broken link to atomic_ops.txt
docs: Turn off section numbering for the input docs
docs: Include uaccess docs from the right file
docs: Do not include from kernel/rcu/srcu.c
Diffstat (limited to 'Documentation/memory-barriers.txt')
| -rw-r--r-- | Documentation/memory-barriers.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index c239a0cf4b1a..c4ddfcd5ee32 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt @@ -1876,8 +1876,8 @@ There are some more advanced barrier functions: This makes sure that the death mark on the object is perceived to be set *before* the reference counter is decremented. - See Documentation/atomic_ops.txt for more information. See the "Atomic - operations" subsection for information on where to use these. + See Documentation/core-api/atomic_ops.rst for more information. See the + "Atomic operations" subsection for information on where to use these. (*) lockless_dereference(); @@ -2584,7 +2584,7 @@ situations because on some CPUs the atomic instructions used imply full memory barriers, and so barrier instructions are superfluous in conjunction with them, and in such cases the special barrier primitives will be no-ops. -See Documentation/atomic_ops.txt for more information. +See Documentation/core-api/atomic_ops.rst for more information. ACCESSING DEVICES |