All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <liwp.linux@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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,
	Wanpeng Li <liwp.linux@gmail.com>
Subject: Re: [PATCH v4 2/2] memcg: change mem_control_xxx to mem_cgroup_xxx
Date: Wed, 27 Jun 2012 08:12:33 +0800	[thread overview]
Message-ID: <20120627001233.GA2289@kernel> (raw)
In-Reply-To: <20120626125437.26050bb0.akpm@linux-foundation.org>

On Tue, Jun 26, 2012 at 12:54:37PM -0700, Andrew Morton wrote:
>On Mon, 25 Jun 2012 19:15:59 +0800
>Wanpeng Li <liwp.linux@gmail.com> wrote:
>
>> From: Wanpeng Li <liwp@linux.vnet.ibm.com>
>> 
>> Unify memcg functions to mem_cgroup_xxx.
>
>How about we unify memcg functions to memcg_xxx?

OK, I will resend the patch. Thank you!

Regards,
Wanpeng Li 

>
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -3999,7 +3999,7 @@ static int mem_cgroup_move_charge_write(struct cgroup *cgrp,
>>  #endif
>>  
>>  #ifdef CONFIG_NUMA
>> -static int mem_control_numa_stat_show(struct cgroup *cont, struct cftype *cft,
>> +static int mem_cgroup_numa_stat_show(struct cgroup *cont, struct cftype *cft,
>>  				      struct seq_file *m)
>
>memcg_numa_stat_show(), etc.
>
>

      reply	other threads:[~2012-06-27  0:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 11:15 [PATCH v4 2/2] memcg: change mem_control_xxx to mem_cgroup_xxx Wanpeng Li
2012-06-25 11:15 ` Wanpeng Li
     [not found] ` <1340622959-13136-1-git-send-email-liwp.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-06-26 19:54   ` Andrew Morton
2012-06-26 19:54     ` Andrew Morton
2012-06-27  0:12     ` Wanpeng Li [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=20120627001233.GA2289@kernel \
    --to=liwp.linux@gmail.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.