This patchset improves logging messages for ACPI CPU, Memory, Container and Dock hotplug notify handlers. The patchset introduces a set of new macro interfaces, acpi_handle_<level>(), and uses them to update the notify handlers. acpi_handle_<level>() appends "ACPI" prefix and ACPI object path to the messages, which has similar usage model as dev_<level>(). This improves diagnosis of hotplug operations since an error message in a log file identifies an object that caused an issue. The patchset is based on the linux-next branch of linux-pm.git tree. v6: - Changed the interface name to acpi_handle_<level>(), and declared them in include/linux/acpi.h. - Added __printf(3,4) to acpi_handle_printk() prototype. - Documented the interfaces acquire the global namespace mutex and may not be called from interrupt context. v5: - Added update for ACPI Dock hotplug error messages. - Added error status / ID info to the messages where needed. v4: - Changed to use dev_<level>() where it is appropriate. v3: - Changed acpi_pr_debug() to NOP when !DEBUG and !DYNAMIC_DEBUG. DYNAMIC_DEBUG will be supported later when necessary. - Added const to a path variable in acpi_printk(). - Added more descriptions to the change log of patch 1/4. v2: - Set buffer.pointer to NULL in acpi_printk(). - Added acpi_pr_debug(). --- Toshi Kani (5): ACPI: Add acpi_handle_<level>() interfaces ACPI: Update CPU hotplug error messages ACPI: Update Memory hotplug error messages ACPI: Update Container hotplug error messages ACPI: Update Dock hotplug error messages --- drivers/acpi/acpi_memhotplug.c | 24 ++++++++++++----------- drivers/acpi/container.c | 10 ++-------- drivers/acpi/dock.c | 30 ++++++++++++++-------------- drivers/acpi/processor_driver.c | 39 +++++++++++++++++++++++-------------- drivers/acpi/utils.c | 37 +++++++++++++++++++++++++++++++++++ include/linux/acpi.h | 43 +++++++++++++++++++++++++++++++++++++++++ 6 files changed, 133 insertions(+), 50 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html