bea3e8a31f
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> |
||
|---|---|---|
| .. | ||
| adis16060_core.c | ||
| adis16080_core.c | ||
| adis16130_core.c | ||
| adis16260.h | ||
| adis16260_core.c | ||
| adis16260_platform_data.h | ||
| adis16260_ring.c | ||
| adis16260_trigger.c | ||
| adxrs450.h | ||
| adxrs450_core.c | ||
| Kconfig | ||
| Makefile | ||