driver core: move uevent call to driver_register

Device driver attribute groups are created after userspace is notified
via an add event. Fix this by moving the kobject_uevent call to
driver_register after the attribute groups are added.

Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/base/bus.c b/drivers/base/bus.c
index 2bcef657a60c79943171085cd8638b3f5efa6903..181ed2660b33b7f4e96e18250b493edd90539def 100644 (file)
--- a/drivers/base/bus.c
+++ b/drivers/base/bus.c
@@ -743,7 +743,6 @@ int bus_add_driver(struct device_driver *drv)
                }
        }
 
-       kobject_uevent(&priv->kobj, KOBJ_ADD);
        return 0;
 
 out_unregister:

diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index 207c27ddf828392ef2ffb74ace6d0b4c8269282a..1b500d6fcc2eec080a2acd6c457b773b64fde85d 100644 (file)
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -187,6 +187,9 @@ int driver_register(struct device_driver *drv)
        ret = driver_add_groups(drv, drv->groups);
        if (ret)
                bus_remove_driver(drv);
+
+       kobject_uevent(&drv->p->kobj, KOBJ_ADD);
+
        return ret;
 }
 EXPORT_SYMBOL_GPL(driver_register);