From: Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: "containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org"
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Benjamin Blum <bblum-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: + cgroups-fix-pid-namespace-bug.patch added to -mm tree
Date: Fri, 24 Jul 2009 13:59:58 +0800 [thread overview]
Message-ID: <4A694DDE.3080605@cn.fujitsu.com> (raw)
In-Reply-To: <20090723225545.f2fd381a.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Andrew Morton wrote:
> On Fri, 24 Jul 2009 13:26:53 +0800 Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
>
>>> Subject: cgroups: fix pid namespace bug
>>> From: Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
>>>
>> Hi Andrew,
>>
>> Could you queue this fix for .31.
>
> Yup, I have it there already.
>
>> I think there's no more objection to this patch or to queuing it
>> for .31 instead of .32. And then Benjamin can rebase his patchset
>> on top of it.
>>
>
> I have a note here that Paul Menage said the patch had "missing operations".
> Did that all get suitably resolved?
>
Yes, resolved by the delta patch "cgroups-fix-pid-namespace-bug-fix.patch"
prev parent reply other threads:[~2009-07-24 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907022320.n62NKpKO022860@imap1.linux-foundation.org>
[not found] ` <200907022320.n62NKpKO022860-AB4EexQrvXRQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2009-07-24 5:26 ` + cgroups-fix-pid-namespace-bug.patch added to -mm tree Li Zefan
[not found] ` <4A69461D.6080201-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-07-24 5:55 ` Andrew Morton
[not found] ` <20090723225545.f2fd381a.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-07-24 5:59 ` Li Zefan [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=4A694DDE.3080605@cn.fujitsu.com \
--to=lizf-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=bblum-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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