From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Andrew@kvack.org, "Morton <akpm"@linux-foundation.org,
linux-mm@kvack.org, Pavel Emelyanov <xemul@openvz.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] memcg: typo in comment to mem_cgroup_print_oom_info()
Date: Fri, 8 Jan 2010 23:09:50 +0530 [thread overview]
Message-ID: <661de9471001080939o55226976scd6e1fc28587a8e8@mail.gmail.com> (raw)
In-Reply-To: <1262963603-21908-1-git-send-email-kirill@shutemov.name>
On Fri, Jan 8, 2010 at 8:43 PM, Kirill A. Shutemov <kirill@shutemov.name> wrote:
> s/mem_cgroup_print_mem_info/mem_cgroup_print_oom_info/
>
> Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
> Cc: Balbir Singh <balbir@linux.vnet.ibm.com>
> Cc: Pavel Emelyanov <xemul@openvz.org>
> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> mm/memcontrol.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 4572907..0d78570 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1070,7 +1070,7 @@ static int mem_cgroup_count_children_cb(struct mem_cgroup *mem, void *data)
> }
>
> /**
> - * mem_cgroup_print_mem_info: Called from OOM with tasklist_lock held in read mode.
> + * mem_cgroup_print_oom_info: Called from OOM with tasklist_lock held in read mode.
> * @memcg: The memory cgroup that went over limit
> * @p: Task that is going to be killed
> *
Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>
--
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>
prev parent reply other threads:[~2010-01-08 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 15:13 [PATCH] memcg: typo in comment to mem_cgroup_print_oom_info() Kirill A. Shutemov
2010-01-08 17:39 ` Balbir Singh [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=661de9471001080939o55226976scd6e1fc28587a8e8@mail.gmail.com \
--to=balbir@linux.vnet.ibm.com \
--cc="Morton <akpm"@linux-foundation.org \
--cc=Andrew@kvack.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).