From: Li Zefan <lizefan@huawei.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Ying Han <yinghan@google.com>, Tejun Heo <htejun@gmail.com>,
Glauber Costa <glommer@parallels.com>
Subject: Re: [PATCH v3 7/7] cgroup: remove css_get_next
Date: Fri, 4 Jan 2013 11:42:40 +0800 [thread overview]
Message-ID: <50E64FB0.9050803@huawei.com> (raw)
In-Reply-To: <1357235661-29564-8-git-send-email-mhocko@suse.cz>
On 2013/1/4 1:54, Michal Hocko wrote:
> Now that we have generic and well ordered cgroup tree walkers there is
> no need to keep css_get_next in the place.
>
> Signed-off-by: Michal Hocko <mhocko@suse.cz>
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Acked-by: Li Zefan <lizefan@huawei.com>
> ---
> include/linux/cgroup.h | 7 -------
> kernel/cgroup.c | 49 ------------------------------------------------
> 2 files changed, 56 deletions(-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-04 3:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 17:54 [PATCH v3 0/7] rework mem_cgroup iterator Michal Hocko
2013-01-03 17:54 ` [PATCH v3 1/7] memcg: synchronize per-zone iterator access by a spinlock Michal Hocko
2013-01-03 17:54 ` [PATCH v3 2/7] memcg: keep prev's css alive for the whole mem_cgroup_iter Michal Hocko
2013-01-03 17:54 ` [PATCH v3 3/7] memcg: rework mem_cgroup_iter to use cgroup iterators Michal Hocko
2013-01-03 17:54 ` [PATCH v3 4/7] memcg: remove memcg from the reclaim iterators Michal Hocko
2013-01-07 6:18 ` Kamezawa Hiroyuki
2013-02-08 19:33 ` Johannes Weiner
2013-02-11 15:16 ` Michal Hocko
2013-02-11 17:56 ` Johannes Weiner
2013-02-11 19:29 ` Michal Hocko
2013-02-11 19:58 ` Johannes Weiner
2013-02-11 21:27 ` Michal Hocko
2013-02-11 22:07 ` Michal Hocko
2013-02-11 22:39 ` Johannes Weiner
2013-02-12 9:54 ` Michal Hocko
2013-02-12 15:10 ` Johannes Weiner
2013-02-12 15:43 ` Michal Hocko
2013-02-12 16:10 ` Paul E. McKenney
2013-02-12 17:25 ` Johannes Weiner
2013-02-12 18:31 ` Paul E. McKenney
2013-02-12 19:53 ` Johannes Weiner
2013-02-13 9:51 ` Michal Hocko
2013-02-12 17:56 ` Michal Hocko
2013-02-12 16:13 ` Michal Hocko
2013-02-12 16:24 ` Michal Hocko
2013-02-12 16:37 ` Michal Hocko
2013-02-12 16:41 ` Johannes Weiner
2013-02-12 17:12 ` Michal Hocko
2013-02-12 17:37 ` Johannes Weiner
2013-02-13 8:11 ` Glauber Costa
2013-02-13 10:38 ` Michal Hocko
2013-02-13 10:34 ` Michal Hocko
2013-02-13 12:56 ` Michal Hocko
2013-02-12 16:33 ` Johannes Weiner
2013-01-03 17:54 ` [PATCH v3 5/7] memcg: simplify mem_cgroup_iter Michal Hocko
2013-01-03 17:54 ` [PATCH v3 6/7] memcg: further " Michal Hocko
2013-01-03 17:54 ` [PATCH v3 7/7] cgroup: remove css_get_next Michal Hocko
2013-01-04 3:42 ` Li Zefan [this message]
2013-01-23 12:52 ` [PATCH v3 0/7] rework mem_cgroup iterator Michal Hocko
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=50E64FB0.9050803@huawei.com \
--to=lizefan@huawei.com \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=htejun@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=yinghan@google.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