From: Li Zefan <lizf@cn.fujitsu.com>
To: Greg Thelen <gthelen@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Paul Menage <menage@google.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ben Blum <bblum@andrew.cmu.edu>,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: alloc_css_id() increments hierarchy depth
Date: Mon, 31 May 2010 09:01:17 +0800 [thread overview]
Message-ID: <4C030A5D.2000700@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTilNrrsNluDBUlXCsZMz7d_-VHn31Ogvkw9AUPnE@mail.gmail.com>
>>>> On Fri, May 28, 2010 at 8:16 AM, Greg Thelen <gthelen@google.com> wrote:
>>>>> Signed-off-by: Greg Thelen <gthelen@google.com>
>>>> Acked-by: Paul Menage <menage@google.com>
>>>>
>>>> Good catch, thanks.
>>>>
>>> Nice Catch.
>>> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>>>
>>> But, who breaks this ? Do we need backport this against old kernels ?
>>>
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=fae9c791703606636c1220e47f6690660042ce7f
>>
>> Hmm. this one. and 2.6.34 needs this patch. Greg, could you post this to
>> stable-2.6.34 tree ?
>
> Given that I forgot to include "Cc: stable <stable@kernel.org>" in the
> patch, I assume the best way to get this patch into -stable is for me
> to email the commit id to stable@kernel.org once the patch is accepted
> into Linus' tree. Let me know if there is a better way.
>
I think Andrew will mark it and send it to stable.
next prev parent reply other threads:[~2010-05-31 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 15:16 Greg Thelen
2010-05-28 22:25 ` Paul Menage
2010-05-30 23:45 ` KAMEZAWA Hiroyuki
2010-05-30 23:54 ` KAMEZAWA Hiroyuki
2010-05-31 0:44 ` Greg Thelen
2010-05-31 0:43 ` KAMEZAWA Hiroyuki
2010-05-31 1:01 ` Li Zefan [this message]
2010-05-31 0:59 ` Li Zefan
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=4C030A5D.2000700@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=bblum@andrew.cmu.edu \
--cc=containers@lists.linux-foundation.org \
--cc=gthelen@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=paulmck@linux.vnet.ibm.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®