staging:iio:adis16200: 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>

diff --git a/drivers/staging/iio/gyro/adis16260_core.c b/drivers/staging/iio/gyro/adis16260_core.c
index 1d58d0e2b397b161d5533e2bb97dd04b0329f976..9571c03aa4cc976346d17bcb27f41d4dc4319060 100644 (file)
--- a/drivers/staging/iio/gyro/adis16260_core.c
+++ b/drivers/staging/iio/gyro/adis16260_core.c
@@ -702,22 +702,16 @@ error_ret:
 
 static int __devexit adis16260_remove(struct spi_device *spi)
 {
-       int ret;
        struct iio_dev *indio_dev = spi_get_drvdata(spi);
 
        iio_device_unregister(indio_dev);
-
-       ret = adis16260_stop_device(indio_dev);
-       if (ret)
-               goto err_ret;
-
+       adis16260_stop_device(indio_dev);
        adis16260_remove_trigger(indio_dev);
        iio_buffer_unregister(indio_dev);
        adis16260_unconfigure_ring(indio_dev);
        iio_device_free(indio_dev);
 
-err_ret:
-       return ret;
+       return 0;
 }
 
 /*