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

2017-06-07 Thread joeyli
On Wed, Jun 07, 2017 at 11:50:13AM +0300, Andy Shevchenko wrote: > On Wed, Jun 7, 2017 at 9:07 AM, 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

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

2017-06-07 Thread Andy Shevchenko
On Wed, Jun 7, 2017 at 9:07 AM, 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] acpi: indicate to platform when hot remove returns busy

2017-06-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] acpi: indicate to platform when hot remove returns busy

2017-06-04 Thread joeyli
On Sun, Jun 04, 2017 at 06:04:53PM +0800, joeyli wrote: > Hi Andy, > > Thanks for your help to review my patch. > > On Sat, Jun 03, 2017 at 08:37:51PM +0300, Andy Shevchenko wrote: > > On Sat, Jun 3, 2017 at 8:20 PM, Lee, Chun-Yi > > wrote: > > > In hotplug logic, it always indicates non-specif

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

2017-06-04 Thread Andy Shevchenko
On Sun, Jun 4, 2017 at 1:04 PM, joeyli wrote: > On Sat, Jun 03, 2017 at 08:37:51PM +0300, Andy Shevchenko wrote: >> On Sat, Jun 3, 2017 at 8:20 PM, Lee, Chun-Yi wrote: >> > -static int acpi_generic_hotplug_event(struct acpi_device *adev, u32 type) >> > +static int acpi_generic_hotplug_event(stru

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

2017-06-04 Thread joeyli
Hi Andy, Thanks for your help to review my patch. On Sat, Jun 03, 2017 at 08:37:51PM +0300, Andy Shevchenko wrote: > On Sat, Jun 3, 2017 at 8:20 PM, Lee, Chun-Yi wrote: > > In hotplug logic, it always indicates non-specific failure to > > platform through _OST when handing acpi hot-remove event

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

2017-06-03 Thread Andy Shevchenko
On Sat, Jun 3, 2017 at 8:20 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] acpi: indicate to platform when hot remove returns busy

2017-06-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