From: Palmer Dabbelt <palmer@sifive.com>
To: stern@rowland.harvard.edu, andrea.parri@amarulasolutions.com,
Will Deacon <will.deacon@arm.com>,
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, akiyks@gmail.com
Cc: davem@davemloft.net, mchehab+samsung@kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
akpm@linux-foundation.org, rdunlap@infradead.org,
linux-kernel@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>,
Daniel Lustig <dlustig@nvidia.com>
Subject: [PATCH] MAINTAINERS: Add Daniel Lustig as a LKMM reviewer
Date: Fri, 22 Jun 2018 14:17:03 -0700 [thread overview]
Message-ID: <20180622211703.4121-1-palmer@sifive.com> (raw)
Dan runs the RISC-V memory model working group. I've been forwarding
him LKMM emails that end up in my inbox, but I'm far from an expert in
this stuff. He requested to be added as a reviewer, which seem sane to
me as it'll take a human out of the loop.
CC: Daniel Lustig <dlustig@nvidia.com>
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9d5eeff51b5f..b980635220e5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8316,6 +8316,7 @@ M: Jade Alglave <j.alglave@ucl.ac.uk>
M: Luc Maranget <luc.maranget@inria.fr>
M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
R: Akira Yokosawa <akiyks@gmail.com>
+R:` Daniel Lustig <dlustig@nvidia.com>
L: linux-kernel@vger.kernel.org
S: Supported
T: git git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
--
2.16.4
next reply other threads:[~2018-06-22 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 21:17 Palmer Dabbelt [this message]
2018-06-22 21:48 ` Daniel Lustig
2018-06-22 22:36 ` Palmer Dabbelt
2018-06-23 0:23 ` Paul E. McKenney
2018-06-23 1:10 ` Andrea Parri
2018-06-23 16:46 ` Paul E. McKenney
2018-06-23 16:53 ` Palmer Dabbelt
2018-06-24 3:36 ` Paul E. McKenney
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=20180622211703.4121-1-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrea.parri@amarulasolutions.com \
--cc=boqun.feng@gmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mchehab+samsung@kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®