From: Laurent Vivier <laurent@vivier.eu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Henning Schild <henning.schild@siemens.com>
Cc: linux-kernel@vger.kernel.org, "Dmitry Safonov" <dima@arista.com>,
linux-fsdevel@vger.kernel.org,
"Eric Biederman" <ebiederm@xmission.com>,
linux-api@vger.kernel.org, "Andrei Vagin" <avagin@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>, "Greg Kurz" <groug@kaod.org>,
"Jann Horn" <jannh@google.com>,
containers@lists.linux-foundation.org,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kiszka" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v7 1/1] ns: add binfmt_misc to the user namespace
Date: Sat, 14 Dec 2019 12:34:41 +0100 [thread overview]
Message-ID: <3205e74b-71f1-14f4-b784-d878b3ef697f@vivier.eu> (raw)
In-Reply-To: <1576267177.4060.4.camel@HansenPartnership.com>
Le 13/12/2019 à 20:59, James Bottomley a écrit :
> On Fri, 2019-12-13 at 18:51 +0100, Henning Schild wrote:
>> Hi all,
>>
>> that is a very useful contribution, which will hopefully be
>> considered.
>
> I'm technically the maintainer on the you touched it last you own it
> basis, so if Christian's concerns get addressed I'll shepherd it
> upstream.
Thank you.
I update this in the next days and re-send the patch.
Thanks,
Laurent
next prev parent reply other threads:[~2019-12-14 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 14:03 [PATCH v7 0/1] ns: introduce binfmt_misc namespace Laurent Vivier
2019-11-07 14:03 ` [PATCH v7 1/1] ns: add binfmt_misc to the user namespace Laurent Vivier
2019-12-03 9:44 ` Laurent Vivier
2019-12-13 17:51 ` Henning Schild
2019-12-13 19:59 ` James Bottomley
2019-12-14 11:34 ` Laurent Vivier [this message]
2019-12-14 12:32 ` Michael Kerrisk (man-pages)
2019-12-16 9:13 ` Laurent Vivier
2019-12-16 15:34 ` Michael Kerrisk (man-pages)
2019-12-03 15:40 ` 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=3205e74b-71f1-14f4-b784-d878b3ef697f@vivier.eu \
--to=laurent@vivier.eu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=avagin@gmail.com \
--cc=clg@kaod.org \
--cc=containers@lists.linux-foundation.org \
--cc=dima@arista.com \
--cc=ebiederm@xmission.com \
--cc=groug@kaod.org \
--cc=henning.schild@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).