Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit d02bde9d authored by David Kershner's avatar David Kershner Committed by Greg Kroah-Hartman
Browse files

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: default avatarDavid Kershner <david.kershner@unisys.com>
Reviewed-by: default avatarTim Sell <timothy.sell@unisys.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 027b03e7

drivers/staging/unisys/visorbus/visorchipset.c

+4 −11
Original line number Diff line number Diff line
@@ -1237,18 +1237,11 @@ parahotplug_process_message(struct controlvm_message *inmsg) 
	if (!req)

		return -ENOMEM;



	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.

	 * 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) {

		err = parahotplug_request_kickoff(req);

		if (err)

			goto err_respond;