lkml.org 
[lkml]   [2017]   [Jul]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 1/2] memory-barriers.txt: Fix broken link to atomic_ops.txt
    Date
    Few obsolete links to atomic_ops.txt exist in memory-barriers.txt though
    the file has moved to core-api/atomic_ops.rst. This commit fixes the
    obsolete links.

    Signed-off-by: SeongJae Park <sj38.park@gmail.com>
    ---
    Documentation/memory-barriers.txt | 6 +++---
    1 file 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
    --
    2.13.0
    \
     
     \ /
      Last update: 2017-07-06 20:21    [W:2.572 / U:0.116 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site