From: "tip-bot2 for Davidlohr Bueso" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Davidlohr Bueso <dbueso@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: locking/core] MAINTAINERS: Add myself as futex reviewer
Date: Sun, 28 Mar 2021 19:14:28 -0000 [thread overview]
Message-ID: <161695886835.398.13402213412656755069.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210122171101.15991-1-dave@stgolabs.net>
The following commit has been merged into the locking/core branch of tip:
Commit-ID: bd9a5fc2edb0bdcb0756298daa31ddd6a02f0634
Gitweb: https://git.kernel.org/tip/bd9a5fc2edb0bdcb0756298daa31ddd6a02f0634
Author: Davidlohr Bueso <dave@stgolabs.net>
AuthorDate: Fri, 22 Jan 2021 09:11:01 -08:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Sun, 28 Mar 2021 21:12:42 +02:00
MAINTAINERS: Add myself as futex reviewer
I'm volunteering to help review some of the pain.
Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210122171101.15991-1-dave@stgolabs.net
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index aa84121..8c31c77 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7363,6 +7363,7 @@ M: Thomas Gleixner <tglx@linutronix.de>
M: Ingo Molnar <mingo@redhat.com>
R: Peter Zijlstra <peterz@infradead.org>
R: Darren Hart <dvhart@infradead.org>
+R: Davidlohr Bueso <dave@stgolabs.net>
L: linux-kernel@vger.kernel.org
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
prev parent reply other threads:[~2021-03-28 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 17:11 [PATCH] " Davidlohr Bueso
2021-03-28 19:14 ` tip-bot2 for Davidlohr Bueso [this message]
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=161695886835.398.13402213412656755069.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®