iio: health: afe4403: Don't return an error in .remove()

The only effect of returning an error in an spi .remove() callback is
that the spi core issues another warning message. Don't report the same
problem twice and return 0 unconditionally instead. Also degrade the log
level to warning, as nothing really bad is expected from a failure to
put the device in suspend mode.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Link: https://lore.kernel.org/r/20211013203223.2694577-12-u.kleine-koenig@pengutronix.de
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

diff --git a/drivers/iio/health/afe4403.c b/drivers/iio/health/afe4403.c
index e891855..97b82f9 100644 (file)
--- a/drivers/iio/health/afe4403.c
+++ b/drivers/iio/health/afe4403.c
@@ -589,10 +589,8 @@ static int afe4403_remove(struct spi_device *spi)
                iio_trigger_unregister(afe->trig);
 
        ret = regulator_disable(afe->regulator);
-       if (ret) {
-               dev_err(afe->dev, "Unable to disable regulator\n");
-               return ret;
-       }
+       if (ret)
+               dev_warn(afe->dev, "Unable to disable regulator\n");
 
        return 0;
 }