staging: unisys: visorbus: remove invalid comment, we are one driver.

Removed a comment that was describing the relationship between the
visorchipset driver and the visorbus driver. Since they are now one
driver the comment no longer makes sense.

Signed-off-by: David Kershner <david.kershner@unisys.com>
Reviewed-by: Reviewed-by: Tim Sell <timothy.sell@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/staging/unisys/visorbus/visorbus_main.c b/drivers/staging/unisys/visorbus/visorbus_main.c
index bb1b6a0bf5de161af7d49ea526a366b5e9d018f4..b99adaaeee153098c01d0228fe9bad2a4283c16e 100644 (file)
--- a/drivers/staging/unisys/visorbus/visorbus_main.c
+++ b/drivers/staging/unisys/visorbus/visorbus_main.c
@@ -1227,14 +1227,6 @@ initiate_chipset_device_pause_resume(struct visor_device *dev, bool is_pause)
                return;
        }
 
-       /*
-        * Note that even though both drv->pause() and drv->resume
-        * specify a callback function, it is NOT necessary for us to
-        * increment our local module usage count.  Reason is, there
-        * is already a linkage dependency between child function
-        * drivers and visorbus, so it is already IMPOSSIBLE to unload
-        * visorbus while child function drivers are still running.
-        */
        if (is_pause) {
                if (!drv->pause) {
                        (*notify_func)(dev, -EINVAL);