All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	akpm@linux-foundation.org, liwanp@linux.vnet.ibm.com,
	tj@kernel.org, zhangyanfei@cn.fujitsu.com, lenb@kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Preparation for arranging hotplug memory in ZONE_MOVABLE.
Date: Tue, 20 Aug 2013 09:07:58 +0800	[thread overview]
Message-ID: <5212C16E.2040105@cn.fujitsu.com> (raw)
In-Reply-To: <15319045.yHqauUVrf3@vostro.rjw.lan>

On 08/20/2013 07:40 AM, Rafael J. Wysocki wrote:
> On Wednesday, August 14, 2013 05:37:05 PM Tang Chen wrote:
>> These three trivial patches are from patch-set "Arrange hotpluggable memory as ZONE_MOVABLE."
>> And they have been acked and reviewed by many people.
>>
>> Hope they can be merged first. And the rest patches are coming soon.
>>
>>
>> Tang Chen (3):
>>    acpi: Print Hot-Pluggable Field in SRAT.
>>    earlycpio.c: Fix the confusing comment of find_cpio_data().
>>    acpi: Kill macro INVALID_TABLE().
>>
>>   arch/x86/mm/srat.c |   11 +++++++----
>>   drivers/acpi/osl.c |   36 ++++++++++++++++++++----------------
>>   lib/earlycpio.c    |   27 ++++++++++++++-------------
>>   3 files changed, 41 insertions(+), 33 deletions(-)
>
> I've queued up this series for 3.12.

Hi Rafael,

Thanks a lot. :)

      reply	other threads:[~2013-08-20  1:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  9:37 [PATCH 0/3] Preparation for arranging hotplug memory in ZONE_MOVABLE Tang Chen
2013-08-14  9:37 ` [PATCH 1/3] acpi: Print Hot-Pluggable Field in SRAT Tang Chen
2013-08-14  9:37 ` [PATCH 2/3] earlycpio.c: Fix the confusing comment of find_cpio_data() Tang Chen
2013-08-14  9:37 ` [PATCH 3/3] acpi: Kill macro INVALID_TABLE() Tang Chen
2013-08-19 23:40 ` [PATCH 0/3] Preparation for arranging hotplug memory in ZONE_MOVABLE Rafael J. Wysocki
2013-08-20  1:07   ` Tang Chen [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=5212C16E.2040105@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwanp@linux.vnet.ibm.com \
    --cc=mingo@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=zhangyanfei@cn.fujitsu.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 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.