Re: [RFC PATCH v4] acpi: indicate to platform when hot remove returns busy

2017-07-07 Thread Rafael J. Wysocki
On Friday, July 07, 2017 02:25:23 PM Lee, Chun-Yi wrote: > In hotplug logic, it always indicates non-specific failure to > platform through _OST when handing acpi hot-remove event failed. Then > platform terminates the hot-remove process but it can not identify > the reason. > > Base on current ho

[RFC PATCH v4] acpi: indicate to platform when hot remove returns busy

2017-07-06 Thread Lee, Chun-Yi
In hotplug logic, it always indicates non-specific failure to platform through _OST when handing acpi hot-remove event failed. Then platform terminates the hot-remove process but it can not identify the reason. Base on current hot-remove code, there have two situations that it returns busy: - OSP

Re: [RFC PATCH v4] acpi: indicate to platform when hot remove returns busy

2017-07-03 Thread Andy Shevchenko
On Mon, Jul 3, 2017 at 4:26 PM, Lee, Chun-Yi wrote: > In hotplug logic, it always indicates non-specific failure to > platform through _OST when handing acpi hot-remove event failed. Then > platform terminates the hot-remove process but it can not identify > the reason. > > Base on current hot-rem

[RFC PATCH v4] acpi: indicate to platform when hot remove returns busy

2017-07-03 Thread Lee, Chun-Yi
In hotplug logic, it always indicates non-specific failure to platform through _OST when handing acpi hot-remove event failed. Then platform terminates the hot-remove process but it can not identify the reason. Base on current hot-remove code, there have two situations that it returns busy: - OSP