hwmon: (asus_atk0110) Fix multi-line comments

Cc: Luca Tettamanti <kronos.it@gmail.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Acked-by: Luca Tettamanti <kronos.it@gmail.com>

diff --git a/drivers/hwmon/asus_atk0110.c b/drivers/hwmon/asus_atk0110.c
index 4000fee9d989628a1741a895d4625cd5bd67cb97..351d1f4593e7a8276da3ff7cdd9b286d4ea2b097 100644 (file)
--- a/drivers/hwmon/asus_atk0110.c
+++ b/drivers/hwmon/asus_atk0110.c
@@ -38,7 +38,8 @@ static const struct dmi_system_id __initconst atk_force_new_if[] = {
        { }
 };
 
-/* Minimum time between readings, enforced in order to avoid
+/*
+ * Minimum time between readings, enforced in order to avoid
  * hogging the CPU.
  */
 #define CACHE_TIME             HZ
@@ -161,7 +162,8 @@ struct atk_sensor_data {
        char const *acpi_name;
 };
 
-/* Return buffer format:
+/*
+ * Return buffer format:
  * [0-3] "value" is valid flag
  * [4-7] value
  * [8- ] unknown stuff on newer mobos
@@ -310,7 +312,8 @@ static union acpi_object *atk_get_pack_member(struct atk_data *data,
 }
 
 
-/* New package format is:
+/*
+ * New package format is:
  * - flag (int)
  *     class - used for de-muxing the request to the correct GITn
  *     type (volt, temp, fan)
@@ -613,7 +616,8 @@ static int atk_read_value_new(struct atk_sensor_data *sensor, u64 *value)
 
        buf = (struct atk_acpi_ret_buffer *)obj->buffer.pointer;
        if (buf->flags == 0) {
-               /* The reading is not valid, possible causes:
+               /*
+                * The reading is not valid, possible causes:
                 * - sensor failure
                 * - enumeration was FUBAR (and we didn't notice)
                 */
@@ -1311,7 +1315,8 @@ static int atk_probe_if(struct atk_data *data)
                dev_dbg(dev, "method " METHOD_WRITE " not found: %s\n",
                                 acpi_format_exception(status));
 
-       /* Check for hwmon methods: first check "old" style methods; note that
+       /*
+        * Check for hwmon methods: first check "old" style methods; note that
         * both may be present: in this case we stick to the old interface;
         * analysis of multiple DSDTs indicates that when both interfaces
         * are present the new one (GGRP/GITM) is not functional.