diff options
| author | David Kershner <david.kershner@unisys.com> | 2017-04-18 16:55:05 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-04-28 11:49:52 +0200 |
| commit | d02bde9d37bc00376727a2b422ee95323bbcd6d6 (patch) | |
| tree | ece337dea926ba18096cdcebc1ca47bc15f3c6e1 /drivers/staging/unisys | |
| parent | 027b03e7171857cf017ad1f338525738be8a25ca (diff) | |
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>
Diffstat (limited to 'drivers/staging/unisys')
| -rw-r--r-- | drivers/staging/unisys/visorbus/visorchipset.c | 15 |
1 files changed, 4 insertions, 11 deletions
diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c index 34b31706f411..5cbc69ff3381 100644 --- 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; |