Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] io:health:afe4404: Remove duplicated error reporting in .remove()
Date: Sat, 14 May 2022 14:38:12 +0100	[thread overview]
Message-ID: <20220514143812.1d2325e6@jic23-huawei> (raw)
In-Reply-To: <20220514130432.304674-1-u.kleine-koenig@pengutronix.de>

On Sat, 14 May 2022 15:04:32 +0200
Uwe Kleine-König         <u.kleine-koenig@pengutronix.de> wrote:

> Returning an error value in an i2c remove callback results in an error
> message being emitted by the i2c core, but otherwise it doesn't make a
> difference.
> 
> As afe4404_remove() already emits an error message on failure and the
> additional error message by the i2c core doesn't add any useful
> information, change the return value to zero to suppress this message.
> 
> This patch is a preparation for making i2c remove callbacks return void.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Applied.

Like the others this will sit in testing until I can rebase the togreg
branch.

Thanks,

Jonathan

> ---
> Hello,
> 
> this is similar to the patches I sent recently.
> (https://lore.kernel.org/linux-iio/20220430081607.15078-1-u.kleine-koenig@pengutronix.de/)
> Just missed this driver when I intended to address this problem type for
> all of drivers/iio/.
> 
> Best regards
> Uwe
> 
>  drivers/iio/health/afe4404.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/iio/health/afe4404.c b/drivers/iio/health/afe4404.c
> index aa9311e1e655..1bb7de60f8ca 100644
> --- a/drivers/iio/health/afe4404.c
> +++ b/drivers/iio/health/afe4404.c
> @@ -591,10 +591,8 @@ static int afe4404_remove(struct i2c_client *client)
>  		iio_trigger_unregister(afe->trig);
>  
>  	ret = regulator_disable(afe->regulator);
> -	if (ret) {
> +	if (ret)
>  		dev_err(afe->dev, "Unable to disable regulator\n");
> -		return ret;
> -	}
>  
>  	return 0;
>  }
> 
> base-commit: 3123109284176b1532874591f7c81f3837bbdc17


  reply	other threads:[~2022-05-14 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 13:04 [PATCH] io:health:afe4404: Remove duplicated error reporting in .remove() Uwe Kleine-König
2022-05-14 13:38 ` Jonathan Cameron [this message]
2022-05-22 19:58   ` Uwe Kleine-König
2022-06-03 15:16     ` Jonathan Cameron
2022-06-03 15:19       ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220514143812.1d2325e6@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox