| commit | 70455e790391dac85d9b483a9e286a40df1ecc7f | |
| author | Jean Delvare <khali@linux-fr.org> | |
| Sun, 18 May 2008 18:49:41 +0000 (18 20:49 +0200) | ||
| committer | Jean Delvare <khali@hyperion.delvare> | |
| Sun, 18 May 2008 18:49:41 +0000 (18 20:49 +0200) | ||
| tree | f5ea301f7aaec341e718fb187d81d3afa65ec6bd | treesnapshot (tar.gz zip) |
| parent | 875b0a473c3ddd80bc4ae88a65cd20027428e160 | commitdiff |
i2c/max6875: Really prevent 24RF08 corruption
i2c-core takes care of the possible corruption of 24RF08 chips for
quite some times, so device devices no longer need to do it. And they
really should not, as applying the prevention twice voids it.
I thought that I had fixed all drivers long ago but apparently I had
missed that one.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Ben Gardner <bgardner@wabtec.com>
i2c-core takes care of the possible corruption of 24RF08 chips for
quite some times, so device devices no longer need to do it. And they
really should not, as applying the prevention twice voids it.
I thought that I had fixed all drivers long ago but apparently I had
missed that one.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Ben Gardner <bgardner@wabtec.com>
| drivers/i2c/chips/max6875.c | diffblobblamehistory |