From: Will Deacon <will.deacon@arm.com>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: stern@rowland.harvard.edu, peterz@infradead.org,
boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com,
j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
mingo@kernel.org
Subject: Re: [PATCH 1/2] tools/memory-model: clarify the origin/scope of the tool name
Date: Thu, 1 Feb 2018 13:40:35 +0000 [thread overview]
Message-ID: <20180201134035.GD9182@arm.com> (raw)
In-Reply-To: <1517486609-10951-1-git-send-email-parri.andrea@gmail.com>
On Thu, Feb 01, 2018 at 01:03:29PM +0100, 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>
> ---
> tools/memory-model/MAINTAINERS | 2 +-
> tools/memory-model/README | 14 +++++++-------
> tools/memory-model/linux-kernel.bell | 2 +-
> tools/memory-model/linux-kernel.cat | 2 +-
> 4 files changed, 10 insertions(+), 10 deletions(-)
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2018-02-01 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 12:03 [PATCH 1/2] tools/memory-model: clarify the origin/scope of the tool name Andrea Parri
2018-02-01 13:40 ` Will Deacon [this message]
2018-02-01 15:26 ` Alan Stern
2018-02-01 23:09 ` Paul E. McKenney
2018-02-02 8:54 ` Andrea Parri
2018-02-02 23:17 ` Paul E. McKenney
2018-02-02 23:20 ` Paul E. McKenney
2018-02-02 10:44 ` Andrea Parri
2018-02-02 23:19 ` Paul E. McKenney
2018-02-02 23:46 ` Andrea Parri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180201134035.GD9182@arm.com \
--to=will.deacon@arm.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.