iio: adxl345: move null check for i2c id at start of probe
authorAlexandru Ardelean <alexandru.ardelean@analog.com>
Tue, 7 Aug 2018 14:06:05 +0000 (17:06 +0300)
committerJonathan Cameron <Jonathan.Cameron@huawei.com>
Sun, 19 Aug 2018 17:32:05 +0000 (18:32 +0100)
commit6b8471e4601db48ef76144fac6e706256c2aae2d
tree89609023e78f36a78213bd7c3507692137735886
parenteb2e188817b13d2f13b61ea6b96b7753ccff48dd
iio: adxl345: move null check for i2c id at start of probe

Fixes ef89f4b96a2 ("iio: adxl345: Add support for the ADXL375").

This was found via static checker.
After looking into the code a bit, it's unlikely that there will be a NULL
dereference if the `id` object in that specific code path.
However, it's safe to add a NULL (paranoid) check just to make sure and
remove any uncertainties.

Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
drivers/iio/accel/adxl345_i2c.c