rt of these patchset.
>[PATCH 1/4] misc: apds9802als: constify i2c_device_id
>[PATCH 2/4] misc: hmc6352: constify i2c_device_id
>[PATCH 3/4] misc: isl29020: constify i2c_device_id
>[PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id
For a series like this that
[PATCH 1/4] misc: apds9802als: constify i2c_device_id
>[PATCH 2/4] misc: hmc6352: constify i2c_device_id
>[PATCH 3/4] misc: isl29020: constify i2c_device_id
>[PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id
For a series like this that is jumping around the kern
[PATCH 3/4] misc: isl29020: constify i2c_device_id
[PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id
regards,
dan carpenter
~arvind
[PATCH 3/4] misc: isl29020: constify i2c_device_id
[PATCH 4/4] staging: iio: tsl2x7x: constify i2c_device_id
regards,
dan carpenter
~arvind
Don't say "[PATCH 4/4]". It's not a patchset or a part of an email
thread.
regards,
dan carpenter
Don't say "[PATCH 4/4]". It's not a patchset or a part of an email
thread.
regards,
dan carpenter
i2c_device_id are not supposed to change at runtime. All functions
working with i2c_device_id provided by work with
const i2c_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/staging/iio/light/tsl2x7x.c | 2 +-
1 file
i2c_device_id are not supposed to change at runtime. All functions
working with i2c_device_id provided by work with
const i2c_device_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/staging/iio/light/tsl2x7x.c | 2 +-
1 file changed, 1 insertion(+), 1
8 matches
Mail list logo