From: Pavel Emelyanov <xemul@parallels.com>
To: Tejun Heo <tj@kernel.org>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>,
Nathan Lynch <ntl@pobox.com>, Oren Laadan <orenl@cs.columbia.edu>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Serge Hallyn <serue@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Glauber Costa <glommer@parallels.com>,
"containers@lists.osdl.org" <containers@lists.osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Serge Hallyn <serge.hallyn@canonical.com>
Subject: Re: [patch 3/4] proc: Introduce the Children: line in /proc/<pid>/status
Date: Mon, 08 Aug 2011 18:46:55 +0400 [thread overview]
Message-ID: <4E3FF6DF.2000303@parallels.com> (raw)
In-Reply-To: <20110808144035.GB22863@htj.dyndns.org>
On 08/08/2011 06:40 PM, Tejun Heo wrote:
> On Mon, Aug 08, 2011 at 01:20:31AM +0400, Cyrill Gorcunov wrote:
>> From: Pavel Emelyanov <xemul@parallels.com>
>>
>> Although we can get the pids of some task's issue, this is just
>> more convenient to have them this way.
>>
>> Signed-off-by: Pavel Emelyanov <xemul@parallels.com>
>> Acked-by: Serge Hallyn <serge.hallyn@canonical.com>
>> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
>
> I'm not necessarily against this one but don't really see much point
> either. Can we delay this for now?
Sure we can. As I stated previously this one just makes our live easier, but
we can live without one.
> Thanks.
>
prev parent reply other threads:[~2011-08-08 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 21:20 [patch 3/4] proc: Introduce the Children: line in /proc/<pid>/status Cyrill Gorcunov
2011-08-08 14:40 ` Tejun Heo
2011-08-08 14:46 ` Pavel Emelyanov [this message]
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=4E3FF6DF.2000303@parallels.com \
--to=xemul@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dlezcano@fr.ibm.com \
--cc=glommer@parallels.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntl@pobox.com \
--cc=orenl@cs.columbia.edu \
--cc=serge.hallyn@canonical.com \
--cc=serue@us.ibm.com \
--cc=tj@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