From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Chinner <dchinner@redhat.com>,
Glauber Costa <glommer@openvz.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: linux-next: manual merge of the akpm tree with the kvm tree
Date: Mon, 17 Jun 2013 20:23:48 +0800 [thread overview]
Message-ID: <51BEFFD4.6090904@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130617180735.c10c058469ce0633c65225a4@canb.auug.org.au>
Hi Stephen,
Thanks for your work!
On 06/17/2013 04:07 PM, Stephen Rothwell wrote:
> - prepare_zap_oldest_mmu_page(kvm, &invalid_list);
> + freed += prepare_zap_oldest_mmu_page(kvm, &invalid_list);
It seems this change is not needed? and "freed" is not defined in mmu_shrink().
Right?
next prev parent reply other threads:[~2013-06-17 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 8:07 linux-next: manual merge of the akpm tree with the kvm tree Stephen Rothwell
2013-06-17 12:23 ` Xiao Guangrong [this message]
2013-06-18 0:16 ` Stephen Rothwell
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=51BEFFD4.6090904@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=gleb@redhat.com \
--cc=glommer@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sfr@canb.auug.org.au \
/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