b3d5496ea5
Some months ago, you killed the address ranges mechanism from all sensors i2c chip drivers (both the module parameters and the in-code address lists). I think it was a very good move, as the ranges can easily be replaced by individual addresses, and this allowed for significant cleanups in the i2c core (let alone the impressive size shrink for all these drivers). Unfortunately you did not do the same for non-sensors i2c chip drivers. These need the address ranges even less, so we could get rid of the ranges here as well for another significant i2c core cleanup. Here comes a patch which does just that. Since the process is exactly the same as what you did for the other drivers set already, I did not split this one in parts. A documentation update is included. The change saves 308 bytes in the i2c core, and an average 1382 bytes for chip drivers which use I2C_CLIENT_INSMOD, 126 bytes for those which do not. This change is required if we want to merge the sensors and non-sensors i2c code (and we want to do this). Signed-off-by: Jean Delvare <khali@linux-fr.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Index: gregkh-2.6/Documentation/i2c/writing-clients =================================================================== |
||
---|---|---|
.. | ||
g450_pll.c | ||
g450_pll.h | ||
i2c-matroxfb.c | ||
Makefile | ||
matroxfb_accel.c | ||
matroxfb_accel.h | ||
matroxfb_base.c | ||
matroxfb_base.h | ||
matroxfb_crtc2.c | ||
matroxfb_crtc2.h | ||
matroxfb_DAC1064.c | ||
matroxfb_DAC1064.h | ||
matroxfb_g450.c | ||
matroxfb_g450.h | ||
matroxfb_maven.c | ||
matroxfb_maven.h | ||
matroxfb_misc.c | ||
matroxfb_misc.h | ||
matroxfb_Ti3026.c | ||
matroxfb_Ti3026.h |