From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: akpm@linux-foundation.org
Cc: gthelen@google.com, hannes@cmpxchg.org,
kosaki.motohiro@jp.fujitsu.com, mhocko@suse.cz,
yinghan@google.com, "linux-mm@kvack.org" <linux-mm@kvack.org>,
Hillf Danton <dhillf@gmail.com>
Subject: Re: + memcg-remove-pcg_file_mapped.patch added to -mm tree
Date: Mon, 20 Feb 2012 09:09:35 +0900 [thread overview]
Message-ID: <20120220090935.1bd379b1.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20120217214600.28F87A01B8@akpm.mtv.corp.google.com>
On Fri, 17 Feb 2012 13:46:00 -0800
akpm@linux-foundation.org wrote:
>
> The patch titled
> Subject: memcg: remove PCG_FILE_MAPPED
> has been added to the -mm tree. Its filename is
> memcg-remove-pcg_file_mapped.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
>
> ------------------------------------------------------
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Subject: memcg: remove PCG_FILE_MAPPED
>
> With the new lock scheme for updating memcg's page stat, we don't need a
> flag PCG_FILE_MAPPED which was duplicated information of page_mapped().
>
Johannes and Hillf pointed out this is required.
Thank you!.
==
next parent reply other threads:[~2012-02-20 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120217214600.28F87A01B8@akpm.mtv.corp.google.com>
2012-02-20 0:09 ` KAMEZAWA Hiroyuki [this message]
2012-02-28 12:24 ` Johannes Weiner
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=20120220090935.1bd379b1.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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