• Jean Delvare's avatar
    [PATCH] I2C: Kill address ranges in non-sensors i2c chip drivers · b3d5496e
    Jean Delvare authored
    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: default avatarJean Delvare <khali@linux-fr.org>
    Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    
    Index: gregkh-2.6/Documentation/i2c/writing-clients
    ===================================================================
    b3d5496e
writing-clients 28.4 KB