diff options
| author | Peter Zijlstra <[email protected]> | 2019-05-24 13:52:31 +0200 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2019-06-03 12:32:57 +0200 |
| commit | fff9b6c7d26943a8eb32b58364b7ec6b9369746a (patch) | |
| tree | 54d08e55187dcb948012ad5948e4b6e25621351b /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 6a6a9d5fb9f26d2c2127497f3a42adbeb5ccc2a4 (diff) | |
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) <[email protected]>
Reviewed-by: Greg Kroah-Hartman <[email protected]>
Acked-by: Will Deacon <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions