[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200825160652.pxhwofc6nz7u3jgj@wittgenstein>
Date: Tue, 25 Aug 2020 18:06:52 +0200
From: Christian Brauner <christian.brauner@...ntu.com>
To: Joe Perches <joe@...ches.com>
Cc: linux-kernel@...r.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Rob Herring <robh@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] MAINTAINERS: add namespace entry
On Tue, Aug 25, 2020 at 09:01:01AM -0700, Joe Perches wrote:
> On Tue, 2020-08-25 at 17:41 +0200, Christian Brauner wrote:
> > Namespace maintainership has never been formalized which has led to confusion
> > when people need to determine where to send patches and who should take a look
> > at them. Especially, since we have a dedicated list
> > containers.lists.linuxfoundation.org already for a long time. In preparation of
> > this patch I added the containers.lists.linuxfoundation.org mailing list to be
> > archived on lore.
> >
> > This will not just make it easier to catch and review patches specific to
> > namespaces and containers but also for changes not specifically touching
> > namespaces but which nevertheless will have impact on namespaces and
> > containers.
> >
> > Add an entry for Eric (who agreed to this) and me and add a first batch of
> > files that are relevant. Currently, only a small set of files are added and
> > only such namespaces that haven't gotten a separate maintainers entry (e.g.
> > time namespaces). I expect this to grow more entries and/or regular expressions
> > over time. For now these entries here are sufficient. I intend to route this
> > patch upstream soon.
> >
> > Cc: "Eric W. Biederman" <ebiederm@...ssion.com>
> > Signed-off-by: Christian Brauner <christian.brauner@...ntu.com>
> > ---
> > MAINTAINERS | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index f0068bceeb61..272211cdc327 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -11892,6 +11892,26 @@ S: Supported
> > W: https://www.cspi.com/ethernet-products/support/downloads/
> > F: drivers/net/ethernet/myricom/myri10ge/
> >
> > +NAMESPACES AND CONTAINERS
> > +M: Christian Brauner <christian.brauner@...ntu.com>
> > +M: Eric W. Biederman <ebiederm@...ssion.com>
> > +L: containers.lists.linuxfoundation.org
> > +S: Supported
> > +T: https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/
> > +T: https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/
> > +F: ipc/namespace.c
> > +F: kernel/nsproxy.c
> > +F: kernel/pid_namespace.c
> > +F: kernel/user_namespace.c
> > +F: kernel/utsname.c
> > +F: include/linux/nsproxy.h
> > +F: include/linux/ipc_namespace.h
> > +F: include/linux/ns_common.h
> > +F: include/linux/nsproxy.h
> > +F: include/linux/pid_namespace.h
> > +F: include/linux/user_namespace.h
> > +F: include/linux/utsname.h
>
> Please sort the filename order alphabetically.
>
> F: include/linux/ipc_namespace.h
> F: include/linux/ns_common.h
> F: include/linux/nsproxy.h
> F: include/linux/nsproxy.h
> F: include/linux/pid_namespace.h
> F: include/linux/user_namespace.h
> F: include/linux/utsname.h
> F: ipc/namespace.c
> F: kernel/nsproxy.c
> F: kernel/pid_namespace.c
> F: kernel/user_namespace.c
> F: kernel/utsname.c
Thanks, fixing now.
Christian
Powered by blists - more mailing lists