From: Joe Perches <joe@perches.com>
To: Christian Brauner <christian@brauner.io>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
gregkh@linuxfoundation.org, mchehab+samsung@kernel.org
Subject: Re: [PATCH] MAINTAINERS: add new entry for pidfd api
Date: Sun, 14 Jul 2019 16:35:07 -0700 [thread overview]
Message-ID: <62147462c38b7764eca3a97405fef536846be034.camel@perches.com> (raw)
In-Reply-To: <20190714223228.f32lkszztbuencbn@brauner.io>
On Mon, 2019-07-15 at 00:32 +0200, Christian Brauner wrote:
> On Sun, Jul 14, 2019 at 03:10:06PM -0700, Joe Perches wrote:
> > On Sun, 2019-07-14 at 21:33 +0200, Christian Brauner wrote:
> > > Add me as a maintainer for pidfd stuff. This way we can easily see when
> > > changes come in and people know who to yell at.
> > []
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > []
> > > @@ -12567,6 +12567,18 @@ F: arch/arm/boot/dts/picoxcell*
[]
> > > +PIDFD API
[]
> > > +K: \b(clone_args|kernel_clone_args)\b
> > > +N: pidfd
> >
> > This one I'd suggest using 2 F: patterns instead
> > as the patterns are more comprehensive and do not
> > use git history when looked up with get_maintainer
>
> Just to clarify, you suggest removing N: pidfd and just leaving in the
> two F: patterns for samples/pidfd and tools/testing/selftests/pidfd/
> below?
>
> > F: samples/pidfd/
> > F: tools/testing/selftests/pidfd/
Yes.
next prev parent reply other threads:[~2019-07-14 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 19:33 Christian Brauner
2019-07-14 22:10 ` Joe Perches
2019-07-14 22:32 ` Christian Brauner
2019-07-14 23:35 ` Joe Perches [this message]
2019-07-15 0:00 ` Christian Brauner
2019-07-15 0:30 ` [PATCH v1] " Christian Brauner
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=62147462c38b7764eca3a97405fef536846be034.camel@perches.com \
--to=joe@perches.com \
--cc=christian@brauner.io \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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 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®