diff options
author | sayli karnik <karniksayli1995@gmail.com> | 2016-10-11 17:07:21 +0530 |
---|---|---|
committer | Jonathan Cameron <jic23@kernel.org> | 2016-10-23 19:33:44 +0100 |
commit | dd4ba3fb22233e69f06399ee0aa7ecb11d2b595c (patch) | |
tree | 236126422e9f445aa4da250056e6c2efc241a1fc /drivers/md/raid10.c | |
parent | bac80fd0cf889d99461e54e4e1ae31392769f635 (diff) | |
download | linux-dd4ba3fb22233e69f06399ee0aa7ecb11d2b595c.tar.gz linux-dd4ba3fb22233e69f06399ee0aa7ecb11d2b595c.tar.bz2 linux-dd4ba3fb22233e69f06399ee0aa7ecb11d2b595c.zip |
iio: bmi160_core: Fix sparse warning due to incorrect type in assignment
There is a type mismatch between the buffer which is of type s16 and the
samples stored, which are declared as __le16.
Fix the following sparse warning:
drivers/iio/imu/bmi160/bmi160_core.c:411:26: warning: incorrect type
in assignment (different base types)
drivers/iio/imu/bmi160/bmi160_core.c:411:26: expected signed short
[signed] [short] [explicitly-signed] <noident>
drivers/iio/imu/bmi160/bmi160_core.c:411:26: got restricted __le16
[addressable] [usertype] sample
This is a cosmetic-type patch since it does not alter code behaviour.
The le16 is going into a 16bit buf element, and is labelled as IIO_LE in the
channel buffer definition.
Signed-off-by: sayli karnik <karniksayli1995@gmail.com>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'drivers/md/raid10.c')
0 files changed, 0 insertions, 0 deletions