public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
	lenb@kernel.org, liwanp@linux.vnet.ibm.com, tj@kernel.org,
	akpm@linux-foundation.org, joe@perches.com, toshi.kani@hp.com,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 0/4] acpi: Fix and cleanup in acpi.
Date: Thu, 05 Sep 2013 09:56:52 +0800	[thread overview]
Message-ID: <5227E4E4.9050705@cn.fujitsu.com> (raw)
In-Reply-To: <17694789.JU3fWJ8s3q@vostro.rjw.lan>

On 09/05/2013 07:50 AM, Rafael J. Wysocki wrote:
> On Tuesday, September 03, 2013 04:45:37 PM Tang Chen wrote:
>> This patch-set fix the following problems:
>>
>> 1. Kill useless function save_add_info() which will block us from using
>>     numa when MEMORY_HOTPLUG is not configured.
>> 2. acpi_table_parse() didn't check if @id is NULL.
>> 3. Fix incorrect comment in acpi_table_parse(), and return -ENOENT if a
>>     table is not found.
>>
>> And also did some cleanup.
>>
>> change log v1 ->  v2:
>> 1. Use pr_fmt() to simply the SRAT message.
>>     Suggested by Joe Perches<joe@perches.com>
>> 2. Improve the log in patch 4, and change the return value of the stub of
>>     acpi_table_parse() in linux/acpi.h
>>     Suggested by Toshi Kani<toshi.kani@hp.com>
>> 3. Merge the two pr_{info|err} patches into one.
>> 4. Remove on of the patch that has been merged by Rafael.
>>
>> Tang Chen (4):
>>    acpi, numa, mem_hotplug: Kill save_add_info().
>>    acpi cleanup: Use pr_{info|err}() instead of printk() in
>>      arch/x86/mm/srat.c
>>    acpi: Check if @id is NULL in acpi_table_parse()
>>    acpi: Return -ENOENT in acpi_table_parse() and fix wrong comment.
>
> Thanks for the patches!
>
> Peter, any objections against [1-2/4]?  If not, I'll queue them up for 3.13.

Hi Rafael,

Thanks for the checking. As Ishimatu has sent some comments for patch 2, 
I'd like
to send a v3 patch-set soon. Please queue the coming v3 patches.

Thanks.


  reply	other threads:[~2013-09-05  1:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  8:45 [PATCH v2 0/4] acpi: Fix and cleanup in acpi Tang Chen
2013-09-03  8:45 ` [PATCH v2 1/4] acpi, numa, mem_hotplug: Kill save_add_info() Tang Chen
2013-09-03  8:45 ` [PATCH v2 2/4] acpi cleanup: Use pr_{info|err}() instead of printk() in arch/x86/mm/srat.c Tang Chen
2013-09-05  0:33   ` Yasuaki Ishimatsu
2013-09-03  8:45 ` [PATCH v2 3/4] acpi: Check if @id is NULL in acpi_table_parse() Tang Chen
2013-09-03  8:45 ` [PATCH v2 4/4] acpi: Return -ENOENT in acpi_table_parse() and fix wrong comment Tang Chen
2013-09-04 21:39   ` Toshi Kani
2013-09-04 23:50 ` [PATCH v2 0/4] acpi: Fix and cleanup in acpi Rafael J. Wysocki
2013-09-05  1:56   ` Tang Chen [this message]
2013-09-05 11:59     ` Rafael J. Wysocki

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=5227E4E4.9050705@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=joe@perches.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=toshi.kani@hp.com \
    --cc=x86@kernel.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