From: Li Zefan <lizf@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daniel Lezcano <daniel.lezcano@free.fr>,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup : remove the ns_cgroup
Date: Thu, 27 Jan 2011 09:08:51 +0800 [thread overview]
Message-ID: <4D40C5A3.4070703@cn.fujitsu.com> (raw)
In-Reply-To: <20110126161837.43830756.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Tue, 25 Jan 2011 10:39:48 +0100
> Daniel Lezcano <daniel.lezcano@free.fr> wrote:
>
>> This patch removes the ns_cgroup as suggested in the following thread:
>
> I had this patch queued up in September last year, but dropped it. Why
> did I do that?
Because you wanted to wait for some time for users (if any) to notice this
coming change.
Author: Daniel Lezcano <daniel.lezcano@free.fr>
Date: Wed Oct 27 15:33:38 2010 -0700
cgroup: notify ns_cgroup deprecated
The ns_cgroup will be removed very soon. Let's warn, for this version,
ns_cgroup is deprecated.
Make ns_cgroup and clone_children exclusive. If the clone_children is set
and the ns_cgroup is mounted, let's fail with EINVAL when the ns_cgroup
subsys is created (a printk will help the user to understand why the
creation fails).
Update the feature remove schedule file with the deprecated ns_cgroup.
Signed-off-by: Daniel Lezcano <daniel.lezcano@free.fr>
Acked-by: Paul Menage <menage@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
next prev parent reply other threads:[~2011-01-27 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 9:39 [PATCH] cgroup : remove the ns_cgroup Daniel Lezcano
2011-01-27 0:16 ` Andrew Morton
2011-01-27 0:18 ` Andrew Morton
2011-01-27 1:08 ` Li Zefan [this message]
2011-01-27 1:45 ` Andrew Morton
2011-01-27 8:50 ` Daniel Lezcano
2011-01-28 15:45 ` Daniel P. Berrange
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=4D40C5A3.4070703@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=daniel.lezcano@free.fr \
--cc=linux-kernel@vger.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