summaryrefslogtreecommitdiffstats
path: root/drivers/hwmon/max1619.c
diff options
context:
space:
mode:
authorJean Delvare <jdelvare@suse.de>2014-04-04 18:01:34 +0200
committerJean Delvare <jdelvare@suse.de>2014-04-04 18:01:34 +0200
commit6cf0a91ebe11cee1df871619af4eb58c9af32666 (patch)
treeace57336a6a44dd606466c9ae79b7998c1a2f2ec /drivers/hwmon/max1619.c
parent5b58157598f93089ccda90aabd98f27865b344da (diff)
downloadblackbird-op-linux-6cf0a91ebe11cee1df871619af4eb58c9af32666.tar.gz
blackbird-op-linux-6cf0a91ebe11cee1df871619af4eb58c9af32666.zip
hwmon: Avoid initializing the same field twice
All hwmon drivers allocate their data structure with some form of kzalloc, so setting data fields to zero explicitly is a waste of time. Signed-off-by: Jean Delvare <jdelvare@suse.de> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'drivers/hwmon/max1619.c')
-rw-r--r--drivers/hwmon/max1619.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/hwmon/max1619.c b/drivers/hwmon/max1619.c
index 6638e997f83f..4c23afe113e2 100644
--- a/drivers/hwmon/max1619.c
+++ b/drivers/hwmon/max1619.c
@@ -273,7 +273,6 @@ static int max1619_probe(struct i2c_client *new_client,
return -ENOMEM;
i2c_set_clientdata(new_client, data);
- data->valid = 0;
mutex_init(&data->update_lock);
/* Initialize the MAX1619 chip */
OpenPOWER on IntegriCloud