aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorAndrea Parri <[email protected]>2018-02-20 15:25:01 -0800
committerIngo Molnar <[email protected]>2018-02-21 09:58:12 +0100
commit48d44d4e8a583c66d9f376e18c1a1fcc445f4b64 (patch)
tree36d58233b049b32ef7dbfa7e40a0c5a794be70ee /tools/perf/scripts/python/export-to-postgresql.py
parent862e6e2a609197f41bc04420b31ff122be9f870f (diff)
tools/memory-model: Clarify the origin/scope of the tool name
Ingo pointed out that: "The "memory model" name is overly generic, ambiguous and somewhat misleading, as we usually mean the virtual memory layout/model when we say "memory model". GCC too uses it in that sense [...]" Make it clear that tools/memory-model/ uses the term "memory model" as shorthand for "memory consistency model" by calling out this convention in tools/memory-model/README. Stick to the original "memory model" term in sources' headers and for the subsystem name. Suggested-by: Ingo Molnar <[email protected]> Signed-off-by: Andrea Parri <[email protected]> Signed-off-by: Paul E. McKenney <[email protected]> Acked-by: Peter Zijlstra <[email protected]> Acked-by: Will Deacon <[email protected]> Acked-by: Alan Stern <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Thomas Gleixner <[email protected]> Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions