Re: [RFC PATCH v3 1/3] acpi: Introduce prepare_remove operation in acpi_device_ops

2012-11-27 Thread Rafael J. Wysocki
On Monday, November 26, 2012 05:10:21 PM Toshi Kani wrote: > On Fri, 2012-11-23 at 18:50 +0100, Vasilis Liaskovitis wrote: > > This function should be registered for devices that need to execute some > > non-acpi related action in order to be safely removed. If this function > > returns zero, the a

Re: [RFC PATCH v3 1/3] acpi: Introduce prepare_remove operation in acpi_device_ops

2012-11-27 Thread Vasilis Liaskovitis
Hi Toshi, On Mon, Nov 26, 2012 at 05:10:21PM -0700, Toshi Kani wrote: > On Fri, 2012-11-23 at 18:50 +0100, Vasilis Liaskovitis wrote: > > This function should be registered for devices that need to execute some > > non-acpi related action in order to be safely removed. If this function > > returns

Re: [RFC PATCH v3 1/3] acpi: Introduce prepare_remove operation in acpi_device_ops

2012-11-26 Thread Toshi Kani
On Fri, 2012-11-23 at 18:50 +0100, Vasilis Liaskovitis wrote: > This function should be registered for devices that need to execute some > non-acpi related action in order to be safely removed. If this function > returns zero, the acpi core can continue with removing the device. > > Make acpi_bus_

[RFC PATCH v3 1/3] acpi: Introduce prepare_remove operation in acpi_device_ops

2012-11-23 Thread Vasilis Liaskovitis
This function should be registered for devices that need to execute some non-acpi related action in order to be safely removed. If this function returns zero, the acpi core can continue with removing the device. Make acpi_bus_remove call the device-specific prepare_remove callback before removing