lkml.org 
[lkml]   [2018]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] tools/memory-model: clarify the origin/scope of the tool name
On Thu, 1 Feb 2018, Andrea Parri wrote:

> 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 clearer that, in the context of tools/memory-model/, the term
> "memory-model" is used as shorthand for "memory consistency model" by
> calling out this convention in tools/memory-model/README.
>
> Stick to the full name in sources' headers and for the subsystem name.
>
> Suggested-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Andrea Parri <parri.andrea@gmail.com>

For both patches:

Acked-by: Alan Stern <stern@rowland.harvard.edu>

\
 
 \ /
  Last update: 2018-02-01 16:27    [W:0.062 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site