[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171018121038.29409-1-colin.king@canonical.com>
Date: Wed, 18 Oct 2017 13:10:38 +0100
From: Colin King <colin.king@...onical.com>
To: George Joseph <george.joseph@...rview5.com>,
Jean Delvare <jdelvare@...e.com>,
Guenter Roeck <linux@...ck-us.net>, linux-hwmon@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] hwmon: (asc7621): remove redundant assignment to newval
From: Colin Ian King <colin.king@...onical.com>
The setting of newval to zero is redundant as the following if/else
stanzas will always update newval to a new value. Remove the
redundant setting, cleans up clang build warning:
drivers/hwmon/asc7621.c:582:2: warning: Value stored to 'newval' is
never read
Signed-off-by: Colin Ian King <colin.king@...onical.com>
---
drivers/hwmon/asc7621.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/hwmon/asc7621.c b/drivers/hwmon/asc7621.c
index 4875e99b59c9..6d34c05a4f83 100644
--- a/drivers/hwmon/asc7621.c
+++ b/drivers/hwmon/asc7621.c
@@ -579,7 +579,6 @@ static ssize_t show_pwm_enable(struct device *dev,
mutex_unlock(&data->update_lock);
val = config | (altbit << 3);
- newval = 0;
if (val == 3 || val >= 10)
newval = 255;
--
2.14.1
Powered by blists - more mailing lists