[PATCH 04/29] drivers: base: add notifier for failed driver bind
Greg Kroah-Hartman
gregkh at linuxfoundation.org
Mon Aug 25 13:05:39 PDT 2014
On Tue, Aug 05, 2014 at 12:47:32PM +0200, Marek Szyprowski wrote:
> This patch adds support for getting a notify for failed device driver
> bind, so all the items done in BUS_NOTIFY_BIND_DRIVER event can be
> cleaned if the driver fails to bind.
But doesn't the bus know if the driver fails to bind, so why would a
notifier be needed here? Can't it unwind any problems then?
> Signed-off-by: Marek Szyprowski <m.szyprowski at samsung.com>
> ---
> drivers/base/dd.c | 10 +++++++---
> include/linux/device.h | 4 +++-
> 2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/base/dd.c b/drivers/base/dd.c
> index e4ffbcf..541a41f 100644
> --- a/drivers/base/dd.c
> +++ b/drivers/base/dd.c
> @@ -237,10 +237,14 @@ static int driver_sysfs_add(struct device *dev)
> return ret;
> }
>
> -static void driver_sysfs_remove(struct device *dev)
> +static void driver_sysfs_remove(struct device *dev, int failed)
I _hate_ having functions with a flag that does something different
depending on it. If you _really_ need this, just make the notifier call
before calling this function, which should work just fine, right?
thanks,
greg k-h
More information about the linux-arm-kernel
mailing list