From: Christian Brauner <christian@brauner.io>
To: linux-kernel@vger.kernel.org
Cc: joe@perches.com, davem@davemloft.net, gregkh@linuxfoundation.org,
mchehab+samsung@kernel.org,
Christian Brauner <christian@brauner.io>
Subject: [PATCH v1] MAINTAINERS: add new entry for pidfd api
Date: Mon, 15 Jul 2019 02:30:21 +0200 [thread overview]
Message-ID: <20190715003021.25040-1-christian@brauner.io> (raw)
In-Reply-To: <8dbfa2d12bb0c76a19f46128af083921c8feb562.camel@perches.com>
Add me as a maintainer for pidfd stuff so people know who to yell at and
to easily keep track of incoming changes.
Signed-off-by: Christian Brauner <christian@brauner.io>
---
v1:
- Joe Perches <joe@perches.com>:
- remove N: pidfd line
---
MAINTAINERS | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1be025959be9..63522c0043d4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12567,6 +12567,17 @@ F: arch/arm/boot/dts/picoxcell*
F: arch/arm/mach-picoxcell/
F: drivers/crypto/picoxcell*
+PIDFD API
+M: Christian Brauner <christian@brauner.io>
+L: linux-kernel@vger.kernel.org
+S: Maintained
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git
+F: samples/pidfd/
+F: tools/testing/selftests/pidfd/
+K: (?i)pidfd
+K: (?i)clone3
+K: \b(clone_args|kernel_clone_args)\b
+
PIN CONTROL SUBSYSTEM
M: Linus Walleij <linus.walleij@linaro.org>
L: linux-gpio@vger.kernel.org
--
2.22.0
prev parent reply other threads:[~2019-07-15 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 19:33 [PATCH] MAINTAINERS: add new entry for pidfd api Christian Brauner
2019-07-14 22:10 ` Joe Perches
2019-07-14 22:32 ` Christian Brauner
2019-07-14 23:35 ` Joe Perches
2019-07-15 0:00 ` Christian Brauner
2019-07-15 0:30 ` Christian Brauner [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=20190715003021.25040-1-christian@brauner.io \
--to=christian@brauner.io \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@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 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.