staging: unisys: visorbus: update comment

Comment was outdated and did not reflect what was actually happening.
Update the comment to reflect reality.

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

diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c
index 34b31706f4113a6c61415f10391cd06d127ac8de..5cbc69ff338186728195b572d8885a4e61b7b5e7 100644 (file)
--- a/drivers/staging/unisys/visorbus/visorchipset.c
+++ b/drivers/staging/unisys/visorbus/visorchipset.c
@@ -1237,18 +1237,11 @@ parahotplug_process_message(struct controlvm_message *inmsg)
        if (!req)
                return -ENOMEM;
 
+       /*
+        * For enable messages, just respond with success right away, we don't
+        * need to wait to see if the enable was successful.
+        */
        if (inmsg->cmd.device_change_state.state.active) {
-               /*
-                * For enable messages, just respond with success
-                * right away. This is a bit of a hack, but there are
-                * issues with the early enable messages we get (with
-                * either the udev script not detecting that the device
-                * is up, or not getting called at all). Fortunately
-                * the messages that get lost don't matter anyway, as
-                *
-                * devices are automatically enabled at
-                * initialization.
-                */
                err = parahotplug_request_kickoff(req);
                if (err)
                        goto err_respond;