From: Andrew Morton <akpm@linux-foundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: "Chen, Hanxiao" <chenhanxiao@cn.fujitsu.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
Oleg Nesterov <oleg@redhat.com>,
"containers@lists.linux-foundation.org"
<containers@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mateusz Guzik <mguzik@redhat.com>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v8 1/2] procfs: show hierarchy of pid namespace
Date: Thu, 20 Nov 2014 14:21:12 -0800 [thread overview]
Message-ID: <20141120142112.74b490298d3360e53dc3169a@linux-foundation.org> (raw)
In-Reply-To: <546E5D46.4070805@nod.at>
On Thu, 20 Nov 2014 22:29:42 +0100 Richard Weinberger <richard@nod.at> wrote:
> >
> > Any comments?
>
> FWIW, Acked-by: Richard Weinberer <richard@nod.at>
>
> The more challenging question is who will pickup this series?
> Eric? Andrew?
I can monkey the patches but I'd very much like to hear Eric's comments.
Also the CRIU people. How is CRIU presently reassembling these
relationships?
Serge, what was your take on the usefulness/applicability of this work?
IOW, why the ack?
The patchset doesn't touch Documentation/. That will need to be fixed,
please. The new interfaces should be completely described in the
kernel documentation.
The new code appears to be included when CONFIG_PID_NS=n. Is there any
point in doing that?
next prev parent reply other threads:[~2014-11-20 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 9:30 [PATCH v8 0/2] ns, procfs: pid conversion between ns and showing pidns hierarchy Chen Hanxiao
2014-11-18 9:30 ` [PATCH v8 1/2] procfs: show hierarchy of pid namespace Chen Hanxiao
2014-11-20 9:57 ` Chen, Hanxiao
2014-11-20 21:29 ` Richard Weinberger
2014-11-20 22:21 ` Andrew Morton [this message]
2014-11-24 9:47 ` Chen, Hanxiao
2014-11-18 9:30 ` [PATCH v8 2/2] /proc/PID/status: show all sets of pid according to ns Chen Hanxiao
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=20141120142112.74b490298d3360e53dc3169a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenhanxiao@cn.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mguzik@redhat.com \
--cc=oleg@redhat.com \
--cc=richard@nod.at \
--cc=serge.hallyn@ubuntu.com \
/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®