From: Wu Fengguang <fengguang.wu@intel.com>
To: Haicheng Li <haicheng.li@linux.intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86, mem-hotplug: separate x86_64 vmalloc_sync_all() into separate functions
Date: Wed, 19 May 2010 20:08:25 +0800 [thread overview]
Message-ID: <20100519120825.GA23778@localhost> (raw)
In-Reply-To: <4BF3D100.9040502@linux.intel.com>
> No behavior change here.
>
> Move some of vmalloc_sync_all() code into a new function
> sync_global_pgds() that will be useful for memory hotplug.
This is a neat change, thank you!
Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
prev parent reply other threads:[~2010-05-19 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 11:52 [PATCH 1/2] x86, mem-hotplug: separate x86_64 vmalloc_sync_all() into separate functions Haicheng Li
2010-05-19 12:08 ` Wu Fengguang [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=20100519120825.GA23778@localhost \
--to=fengguang.wu@intel.com \
--cc=ak@linux.intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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