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, corbet@lwn.net
Subject: Re: [PATCH 2/2] MAINTAINERS: add the Memory Consistency Model subsystem
Date: Thu, 1 Feb 2018 13:44:01 +0000 [thread overview]
Message-ID: <20180201134401.GE9182@arm.com> (raw)
In-Reply-To: <1517486666-11011-1-git-send-email-parri.andrea@gmail.com>
On Thu, Feb 01, 2018 at 01:04:26PM +0100, Andrea Parri wrote:
> Integrate (and then remove) tools/memory-model/MAINTAINERS into the
> main MAINTAINERS file. This way get_maintainer.pl can give a "right
> answer" for tools/memory-model/.
>
> Suggested-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Andrea Parri <parri.andrea@gmail.com>
> ---
> MAINTAINERS | 16 ++++++++++++++++
> tools/memory-model/MAINTAINERS | 15 ---------------
> 2 files changed, 16 insertions(+), 15 deletions(-)
> delete mode 100644 tools/memory-model/MAINTAINERS
Acked-by: Will Deacon <will.deacon@arm.com>
Makes a lot more sense having this in the top-level MAINTAINERS file.
It might also make sense to add:
F: Documentation/memory-barriers.txt
as a separate patch now that we have a hit-list of memory model people
who can help poor old Jon (who currently gets blamed by get_maintainer.pl).
Will
next prev parent reply other threads:[~2018-02-01 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 12:04 [PATCH 2/2] MAINTAINERS: add the Memory Consistency Model subsystem Andrea Parri
2018-02-01 13:44 ` Will Deacon [this message]
2018-02-01 19:39 ` 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=20180201134401.GE9182@arm.com \
--to=will.deacon@arm.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--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.