staging: unisys: visorbus: simplify commenting in controlvm_init

During the process of udpating the features bits, put a block comment for
all updates instead of a separate comment for each one.

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 74cce4f1a7bd7340a30ef13bece954da4f69a7c0..315000fd8122dfbb75744822bb96ff08acc6683a 100644 (file)
--- a/drivers/staging/unisys/visorbus/visorchipset.c
+++ b/drivers/staging/unisys/visorbus/visorchipset.c
@@ -377,15 +377,11 @@ static int chipset_init(struct controlvm_message *inmsg)
 
        /*
         * Set features to indicate we support parahotplug (if Command also
-        * supports it).
+        * supports it). Set the "reply" bit so Command knows this is a
+        * features-aware driver.
         */
        features = inmsg->cmd.init_chipset.features &
                   VISOR_CHIPSET_FEATURE_PARA_HOTPLUG;
-
-       /*
-        * Set the "reply" bit so Command knows this is a features-aware
-        * driver.
-        */
        features |= VISOR_CHIPSET_FEATURE_REPLY;
 
 out_respond: