remarkable-linux/drivers/staging/iio/imu
Lars-Peter Clausen 0b4ac3dce4 staging:iio:adis16400: Do not return a error in remove function
In the Linux device driver model the remove callback is not allowed to fail and
the device will be removed regardless of the return value of the remove
callback. So if we abort in the remove function and do not free all resources we
will create a resource leak. Also all kinds of undefined behaviour are expected
to happen since the IIO device is still there while its parent is already gone.

The error which the driver tries to handle in the remove function is
non-critical, so we can just ignore it and continue to free all resources and
remove the IIO device.

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
2012-09-22 10:17:28 +01:00
..
adis16400.h staging:iio: Update email address for Jonathan Cameron. 2012-09-03 20:26:46 +01:00
adis16400_core.c staging:iio:adis16400: Do not return a error in remove function 2012-09-22 10:17:28 +01:00
adis16400_ring.c iio: Drop timestamp parameter from buffer store_to callback 2012-09-08 10:14:34 +01:00
adis16400_trigger.c staging:iio: Streamline API function naming 2012-04-29 21:23:49 -04:00
Kconfig staging:iio:imu:adis16400 rename adis16344 -> adis16334. 2011-10-03 16:07:05 -07:00
Makefile staging:iio: tree wide IIO_RING_BUFFER config symbol to IIO_BUFFER 2011-09-26 17:31:53 -07:00