From: Stefan Agner Date: Wed, 20 Jan 2016 01:14:39 +0000 (-0800) Subject: regmap: clairify meaning of max_register X-Git-Tag: next-20160210~26^2^2 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=b429fab4467e2320f67c058d7419c03c7221d125;p=karo-tx-linux.git regmap: clairify meaning of max_register The exact meaning of max_register is not entierly clear. Follow the common wording and use "address" instead of "index". Signed-off-by: Stefan Agner Signed-off-by: Mark Brown --- diff --git a/include/linux/regmap.h b/include/linux/regmap.h index 18394343f489..27aaac9027c4 100644 --- a/include/linux/regmap.h +++ b/include/linux/regmap.h @@ -162,7 +162,7 @@ typedef void (*regmap_unlock)(void *); * This field is a duplicate of a similar file in * 'struct regmap_bus' and serves exact same purpose. * Use it only for "no-bus" cases. - * @max_register: Optional, specifies the maximum valid register index. + * @max_register: Optional, specifies the maximum valid register address. * @wr_table: Optional, points to a struct regmap_access_table specifying * valid ranges for write access. * @rd_table: As above, for read access.