CC doc folks On Wed, Jun 7, 2017 at 12:59 AM, Palmer Dabbelt <palmer@xxxxxxxxxxx> wrote: > I was reading the memory barries documentation in order to make sure the > RISC-V barries were correct, and I found a broken link to the atomic > operations documentation. > > Signed-off-by: Palmer Dabbelt <palmer@xxxxxxxxxxx> > --- > Documentation/memory-barriers.txt | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt > index 732f10ea382e..f1c9eaa45a57 100644 > --- a/Documentation/memory-barriers.txt > +++ b/Documentation/memory-barriers.txt > @@ -498,11 +498,11 @@ And a couple of implicit varieties: > This means that ACQUIRE acts as a minimal "acquire" operation and > RELEASE acts as a minimal "release" operation. > > -A subset of the atomic operations described in atomic_ops.txt have ACQUIRE > -and RELEASE variants in addition to fully-ordered and relaxed (no barrier > -semantics) definitions. For compound atomics performing both a load and a > -store, ACQUIRE semantics apply only to the load and RELEASE semantics apply > -only to the store portion of the operation. > +A subset of the atomic operations described in core-api/atomic_ops.rst have > +ACQUIRE and RELEASE variants in addition to fully-ordered and relaxed (no > +barrier semantics) definitions. For compound atomics performing both a load > +and a store, ACQUIRE semantics apply only to the load and RELEASE semantics > +apply only to the store portion of the operation. > > Memory barriers are only required where there's a possibility of interaction > between two CPUs or between a CPU and a device. If it can be guaranteed that > -- > 2.13.0
