staging: vme: fix comment in __vme_register_driver()

Signed-off-by: Manohar Vanga <manohar.vanga@cern.ch>
Acked-by: Martyn Welch <martyn.welch@ge.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

diff --git a/drivers/staging/vme/vme.c b/drivers/staging/vme/vme.c
index b04b4688f705d9a7142b6d4335a9f4062de41f4b..3cbc69c65d780f759fa5c8b6a0329f0f4885421c 100644 (file)
--- a/drivers/staging/vme/vme.c
+++ b/drivers/staging/vme/vme.c
@@ -1421,10 +1421,7 @@ static int __vme_register_driver(struct vme_driver *drv, unsigned int ndevs)
                 * and if the bridge is removed, it will have to go through
                 * vme_unregister_bridge() to do it (which calls remove() on
                 * the bridge which in turn tries to acquire vme_buses_lock and
-                * will have to wait). The probe() called after device
-                * registration in __vme_register_driver below will also fail
-                * as the bridge is being removed (since the probe() calls
-                * vme_bridge_get()).
+                * will have to wait).
                 */
                err = __vme_register_driver_bus(drv, bridge, ndevs);
                if (err)