[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <500F6BE3.8060508@jp.fujitsu.com>
Date: Wed, 25 Jul 2012 12:45:39 +0900
From: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
To: Toshi Kani <toshi.kani@...com>
CC: <lenb@...nel.org>, <linux-acpi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <bhelgaas@...gle.com>,
<liuj97@...il.com>, <srivatsa.bhat@...ux.vnet.ibm.com>,
<prarit@...hat.com>, <imammedo@...hat.com>,
<vijaymohan.pandarathil@...com>
Subject: Re: [PATCH 0/4] ACPI: hotplug messages improvement
Hi Toshi,
2012/07/19 5:40, Toshi Kani wrote:
> This patchset improves logging messages for ACPI CPU, Memory, and
> Container hotplug notify handlers. The patchset introduces a set of
> new macro interfaces, acpi_pr_<level>(), and updates the notify
> handlers to use them. acpi_pr_<level>() appends "ACPI" prefix and
> ACPI object path to the messages. This improves diagnostics in
> hotplug operations since it identifies an object that caused an
> issue in a log file.
>
The log message looks good to me.
But I could not understand when to use it instead of pr_{warn, info, ...}
or ACPI_{WARNING, INFO, ...}. Do you have the policy?
> ---
> This patchset applies on top of the patch below.
>
> [PATCH] ACPI: Add ACPI CPU hot-remove support
> http://marc.info/?l=linux-acpi&m=134098193327362&w=2
>
> ---
> Toshi Kani (4):
> ACPI: Add acpi_pr_<level>() interfaces
> ACPI: Update CPU hotplug messages
> ACPI: Update Memory hotplug messages
> ACPI: Update Container hotplug messages
I think you need update other component, which are driver/acpi/{acpi_pad.c,
battery.c, button.c}. Do you have the plan to update them?
Thanks,
Yasuaki Ishimatsu
> ---
> drivers/acpi/acpi_memhotplug.c | 24 ++++++++++++------------
> drivers/acpi/container.c | 6 +++---
> drivers/acpi/processor_driver.c | 36 +++++++++++++++++++++---------------
> drivers/acpi/utils.c | 32 ++++++++++++++++++++++++++++++++
> include/acpi/acpi_bus.h | 18 ++++++++++++++++++
> 5 files changed, 86 insertions(+), 30 deletions(-)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists