From: Glauber Costa <glommer@parallels.com>
To: Wanpeng Li <liwp.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Balbir Singh <bsingharora@gmail.com>,
<linux-kernel@vger.kernel.org>, <cgroups@vger.kernel.org>
Subject: Re: [PATCH v2] memcg: unify mem_control_xxx to memcg_xxx
Date: Wed, 27 Jun 2012 12:43:50 +0400 [thread overview]
Message-ID: <4FEAC7C6.7030601@parallels.com> (raw)
In-Reply-To: <1340756175-3420-1-git-send-email-liwp.linux@gmail.com>
On 06/27/2012 04:16 AM, Wanpeng Li wrote:
> From: Wanpeng Li <liwp@linux.vnet.ibm.com>
>
> Changelog:
>
> V2 -> V1:
>
> * replace memory_cgroup_xxx by memcg_xxx
>
> Unify memcg functions to memcg_xxx.
This patch achieves nothing.
You're changing a couple of function names. Andrew stated goal was to
change *all* function names from mem_cgroup_xxx to memcg_xxx, not just
one or two.
This can be done mechanically by replacing occurrences of mem_cgroup_xxx
with memcg_xxx, and verifying that your final result is correct by
compiling the kernel with and without the combination of config options
that matters here, plus a set of randconfigs - or anything like that.
Make sure you have Andrew's latest patch in your tree, that converts the
config option names.
next prev parent reply other threads:[~2012-06-27 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 0:16 [PATCH v2] memcg: unify mem_control_xxx to memcg_xxx Wanpeng Li
2012-06-27 8:43 ` Glauber Costa [this message]
2012-06-27 8:59 ` Michal Hocko
2012-06-27 9:00 ` Glauber Costa
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=4FEAC7C6.7030601@parallels.com \
--to=glommer@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwp.linux@gmail.com \
--cc=mhocko@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).