Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Yuan Can <yuancan@huawei.com>
Cc: <dan@dlrobertson.com>, <lars@metafoo.de>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: accel: bma400: Switch to use dev_err_probe() helper
Date: Sat, 24 Sep 2022 17:03:40 +0100	[thread overview]
Message-ID: <20220924170340.1bdf5e84@jic23-huawei> (raw)
In-Reply-To: <20220921023915.47300-1-yuancan@huawei.com>

On Wed, 21 Sep 2022 02:39:15 +0000
Yuan Can <yuancan@huawei.com> wrote:

> In the probe path, dev_err() can be replace with dev_err_probe()
> which will check if error code is -EPROBE_DEFER and prints the
> error name.
> 
> Signed-off-by: Yuan Can <yuancan@huawei.com>

@Dan.  whilst reviewing this one I noticed we are turning the power to vddio (which
I assume is the supply for the IO interface) after reading the chip ID. That
doesn't seem right!

Unrelated to this patch beyond I was looking to see if there were other cases
for dev_err_probe() in here.

Applied but it may well not make the next merge window as I'm not sure I'll get
another IIO pull request out before that opens.  Currently Linus has hinted
at a possible rc8 but we will know more on that after he tags rc7 tomorrow.

Jonathan

> ---
>  drivers/iio/accel/bma400_core.c | 10 +++-------
>  1 file changed, 3 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/iio/accel/bma400_core.c b/drivers/iio/accel/bma400_core.c
> index eceb1f8d338d..cebd7e370b09 100644
> --- a/drivers/iio/accel/bma400_core.c
> +++ b/drivers/iio/accel/bma400_core.c
> @@ -886,14 +886,10 @@ static int bma400_init(struct bma400_data *data)
>  	ret = devm_regulator_bulk_get(data->dev,
>  				      ARRAY_SIZE(data->regulators),
>  				      data->regulators);
> -	if (ret) {
> -		if (ret != -EPROBE_DEFER)
> -			dev_err(data->dev,
> -				"Failed to get regulators: %d\n",
> -				ret);
> +	if (ret)
> +		return dev_err_probe(data->dev, ret, "Failed to get regulators: %d\n",
> +				     ret);
>  
> -		return ret;
> -	}
>  	ret = regulator_bulk_enable(ARRAY_SIZE(data->regulators),
>  				    data->regulators);
>  	if (ret) {


      reply	other threads:[~2022-09-24 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  2:39 [PATCH] iio: accel: bma400: Switch to use dev_err_probe() helper Yuan Can
2022-09-24 16:03 ` Jonathan Cameron [this message]

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=20220924170340.1bdf5e84@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=dan@dlrobertson.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=yuancan@huawei.com \
    /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