From: Laurent Vivier <laurent@vivier.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-api@vger.kernel.org, Eric Biederman <ebiederm@xmission.com>,
Dmitry Safonov <dima@arista.com>,
Andrei Vagin <avagin@openvz.org>,
containers@lists.linux-foundation.org
Subject: Re: [RFC 1/2] ns: introduce binfmt_misc namespace
Date: Mon, 1 Oct 2018 09:00:02 +0200 [thread overview]
Message-ID: <fc872743-d304-3d8c-6a41-91bd4fea148d@vivier.eu> (raw)
In-Reply-To: <20181001012113.GA21178@kroah.com>
Le 01/10/2018 à 03:21, Greg KH a écrit :
> On Mon, Oct 01, 2018 at 01:46:27AM +0200, Laurent Vivier wrote:
>> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
>> ---
>
> I don't take patches without any changelog text, I don't know if other
> maintainers are as nice. But for a new feature, you really should write
> something...
Yes, I know. But it's an RFC and all the explanations are in the cover
letter for now. I will fill the changelog once I know if the feature is
interesting or not.
Thank you for your comment.
Laurent
next prev parent reply other threads:[~2018-10-01 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 23:46 [RFC 0/2] ns: introduce binfmt_misc namespace Laurent Vivier
2018-09-30 23:46 ` [RFC 1/2] " Laurent Vivier
2018-10-01 1:21 ` Greg KH
2018-10-01 7:00 ` Laurent Vivier [this message]
2018-09-30 23:46 ` [RFC 2/2] binfmt_misc: move data to binfmt_namespace Laurent Vivier
2018-10-01 8:54 ` Jann Horn
2018-10-01 4:45 ` [RFC 0/2] ns: introduce binfmt_misc namespace Andy Lutomirski
2018-10-01 7:13 ` Laurent Vivier
2018-10-01 12:26 ` Dmitry Safonov
2018-10-01 7:21 ` Eric W. Biederman
2018-10-01 8:45 ` Laurent Vivier
2018-10-01 8:56 ` Eric W. Biederman
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=fc872743-d304-3d8c-6a41-91bd4fea148d@vivier.eu \
--to=laurent@vivier.eu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=avagin@openvz.org \
--cc=containers@lists.linux-foundation.org \
--cc=dima@arista.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--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).