summaryrefslogtreecommitdiff
path: root/arch/s390
diff options
context:
space:
mode:
authorPeter Zijlstra <peterz@infradead.org>2019-05-24 14:52:31 +0300
committerIngo Molnar <mingo@kernel.org>2019-06-03 13:32:57 +0300
commitfff9b6c7d26943a8eb32b58364b7ec6b9369746a (patch)
tree54d08e55187dcb948012ad5948e4b6e25621351b /arch/s390
parent6a6a9d5fb9f26d2c2127497f3a42adbeb5ccc2a4 (diff)
downloadlinux-fff9b6c7d26943a8eb32b58364b7ec6b9369746a.tar.xz
Documentation/atomic_t.txt: Clarify pure non-rmw usage
Clarify that pure non-RMW usage of atomic_t is pointless, there is nothing 'magical' about atomic_set() / atomic_read(). This is something that seems to confuse people, because I happen upon it semi-regularly. Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Acked-by: Will Deacon <will.deacon@arm.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/20190524115231.GN2623@hirez.programming.kicks-ass.net Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'arch/s390')
0 files changed, 0 insertions, 0 deletions