Subject: hwmon: Cleanup a bogus legacy comment Cleanup a bogus legacy comment that has been replicated to many hardware monitoring drivers. Signed-off-by: Jean Delvare --- drivers/hwmon/it87.c | 6 ++---- drivers/hwmon/lm78.c | 6 ++---- drivers/hwmon/lm85.c | 7 ++----- drivers/hwmon/sis5595.c | 6 ++---- drivers/hwmon/via686a.c | 5 ++--- drivers/hwmon/w83627hf.c | 5 ++--- drivers/hwmon/w83781d.c | 10 ++-------- 7 files changed, 14 insertions(+), 31 deletions(-) --- linux-2.6.19-git.orig/drivers/hwmon/it87.c 2006-12-10 12:12:52.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/it87.c 2006-12-10 13:46:28.000000000 +0100 @@ -214,10 +214,8 @@ }; -/* For each registered IT87, we need to keep some data in memory. That - data is pointed to by it87_list[NR]->data. The structure itself is - dynamically allocated, at the same time when a new it87 client is - allocated. */ +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct it87_data { struct i2c_client client; struct class_device *class_dev; --- linux-2.6.19-git.orig/drivers/hwmon/lm78.c 2006-11-30 21:16:06.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/lm78.c 2006-12-10 13:46:33.000000000 +0100 @@ -125,10 +125,8 @@ bad. Quite a lot of bookkeeping is done. A real driver can often cut some corners. */ -/* For each registered LM78, we need to keep some data in memory. That - data is pointed to by lm78_list[NR]->data. The structure itself is - dynamically allocated, at the same time when a new lm78 client is - allocated. */ +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct lm78_data { struct i2c_client client; struct class_device *class_dev; --- linux-2.6.19-git.orig/drivers/hwmon/lm85.c 2006-11-30 21:16:06.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/lm85.c 2006-12-10 13:46:38.000000000 +0100 @@ -298,11 +298,6 @@ #define LM85_DATA_INTERVAL (HZ + HZ / 2) #define LM85_CONFIG_INTERVAL (1 * 60 * HZ) -/* For each registered LM85, we need to keep some data in memory. That - data is pointed to by lm85_list[NR]->data. The structure itself is - dynamically allocated, at the same time when a new lm85 client is - allocated. */ - /* LM85 can automatically adjust fan speeds based on temperature * This structure encapsulates an entire Zone config. There are * three zones (one for each temperature input) on the lm85 @@ -329,6 +324,8 @@ u8 min_off; /* Min PWM or OFF below "limit", flag */ }; +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct lm85_data { struct i2c_client client; struct class_device *class_dev; --- linux-2.6.19-git.orig/drivers/hwmon/sis5595.c 2006-11-30 21:16:06.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/sis5595.c 2006-12-10 13:46:44.000000000 +0100 @@ -162,10 +162,8 @@ } #define DIV_FROM_REG(val) (1 << (val)) -/* For the SIS5595, we need to keep some data in memory. That - data is pointed to by sis5595_list[NR]->data. The structure itself is - dynamically allocated, at the time when the new sis5595 client is - allocated. */ +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct sis5595_data { struct i2c_client client; struct class_device *class_dev; --- linux-2.6.19-git.orig/drivers/hwmon/via686a.c 2006-11-30 21:16:06.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/via686a.c 2006-12-10 13:48:41.000000000 +0100 @@ -292,9 +292,8 @@ #define DIV_FROM_REG(val) (1 << (val)) #define DIV_TO_REG(val) ((val)==8?3:(val)==4?2:(val)==1?0:1) -/* For the VIA686A, we need to keep some data in memory. - The structure is dynamically allocated, at the same time when a new - via686a client is allocated. */ +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct via686a_data { struct i2c_client client; struct class_device *class_dev; --- linux-2.6.19-git.orig/drivers/hwmon/w83627hf.c 2006-12-04 20:10:21.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/w83627hf.c 2006-12-10 13:46:48.000000000 +0100 @@ -286,9 +286,8 @@ return ((u8) i); } -/* For each registered chip, we need to keep some data in memory. That - data is pointed to by w83627hf_list[NR]->data. The structure itself is - dynamically allocated, at the same time when a new client is allocated. */ +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct w83627hf_data { struct i2c_client client; struct class_device *class_dev; --- linux-2.6.19-git.orig/drivers/hwmon/w83781d.c 2006-11-30 21:16:06.000000000 +0100 +++ linux-2.6.19-git/drivers/hwmon/w83781d.c 2006-12-10 13:47:58.000000000 +0100 @@ -221,14 +221,8 @@ a bit - except if there could be more than one SMBus. Groan. No solution for this yet. */ -/* This module may seem overly long and complicated. In fact, it is not so - bad. Quite a lot of bookkeeping is done. A real driver can often cut - some corners. */ - -/* For each registered W83781D, we need to keep some data in memory. That - data is pointed to by w83781d_list[NR]->data. The structure itself is - dynamically allocated, at the same time when a new w83781d client is - allocated. */ +/* For each registered chip, we need to keep some data in memory. + The structure is dynamically allocated. */ struct w83781d_data { struct i2c_client client; struct class_device *class_dev;