Re: [PATCH v3 1/3] Use acpi_os_hotplug_execute() instead of alloc_acpi_hp_work().

2012-10-31 Thread Tang Chen
On 11/01/2012 11:52 AM, Yinghai Lu wrote: On Wed, Oct 31, 2012 at 12:27 AM, Tang Chen wrote: Please check if you can just fold acpi_hp_cb_execute callers, and use acpi_os_hotplug_execute directly. and have two local conext struct too. I think this could bring some duplicated work. We need

Re: [PATCH v3 1/3] Use acpi_os_hotplug_execute() instead of alloc_acpi_hp_work().

2012-10-31 Thread Yinghai Lu
On Wed, Oct 31, 2012 at 12:27 AM, Tang Chen wrote: > Hi Yinghai, > > alloc_acpi_hp_work() just puts the hutplug work onto kacpi_hotplug_wq. > As mentioned by Toshi Kani, this job has been done in > acpi_os_hotplug_execute(). > So we should use it instead of alloc_acpi_hp_work(). > > This patch ad

[PATCH v3 1/3] Use acpi_os_hotplug_execute() instead of alloc_acpi_hp_work().

2012-10-31 Thread Tang Chen
Hi Yinghai, alloc_acpi_hp_work() just puts the hutplug work onto kacpi_hotplug_wq. As mentioned by Toshi Kani, this job has been done in acpi_os_hotplug_execute(). So we should use it instead of alloc_acpi_hp_work(). This patch adds a acpi_hp_cb_data struct, which encapsulates the hotplug event n