tree afec022fc9f6a87d2e57f96b4f9ebc798d50c95f
parent 575c1b8ebaeb00e2a0c8944565ee5a4753ae77a1
author Akira Yokosawa <akiyks@gmail.com> 1492307749 +0900
committer Paul E. McKenney <paulmck@linux.vnet.ibm.com> 1492443303 -0700

advsync: Use READ_ONCE()/WRITE_ONCE() in sequence in 'Guarantees'

Using pseudo-asm code for sequences here also gives redundant look.
Using READ_ONCE/WRITE_ONCE() instead is a good idea.
In memory-barriers.txt, sequences corresponding to the latter part
of this section are not yet enclosed by READ_ONCE()/WRITE_ONCE(),
but memory subsystem can merge overlapping accesses even if these
directives are used.

Also use "," as delimiters in the memory access ordering lists.

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>