On Tue, Aug 05, 2014 at 12:47:32PM +0200, Marek Szyprowski wrote:
This patch adds support for getting a notify for failed device driverBut doesn't the bus know if the driver fails to bind, so why would a
bind, so all the items done in BUS_NOTIFY_BIND_DRIVER event can be
cleaned if the driver fails to bind.
notifier be needed here? Can't it unwind any problems then?
Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>I _hate_ having functions with a flag that does something different
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
@@ -237,10 +237,14 @@ static int driver_sysfs_add(struct device *dev)
-static void driver_sysfs_remove(struct device *dev)
+static void driver_sysfs_remove(struct device *dev, int failed)
depending on it. If you _really_ need this, just make the notifier call
before calling this function, which should work just fine, right?