OpenE2K
/
linux
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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>
This commit is contained in:
David Kershner 2017-04-18 16:55:05 -04:00 committed by Greg Kroah-Hartman
parent 027b03e717
commit d02bde9d37
1 changed files with 4 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
drivers/staging/unisys/visorbus/visorchipset.c
View File

@ -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;