From: Jonathan Cameron <jic23@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-iio@vger.kernel.org>, <dan@dlrobertson.com>,
<lars@metafoo.de>, <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH -next] iio: accel: bma400: Switch to use dev_err_probe() helper
Date: Sun, 2 Oct 2022 13:30:46 +0100 [thread overview]
Message-ID: <20221002133046.31d536f0@jic23-huawei> (raw)
In-Reply-To: <20220927064435.152211-1-yangyingliang@huawei.com>
On Tue, 27 Sep 2022 14:44:35 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:
> In the probe path, dev_err() can be replaced with dev_err_probe()
> which will check if error code is -EPROBE_DEFER and prints the
> error name. It also sets the defer probe reason which can be
> checked later through debugfs. It's more simple in error path.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Similar patch already queued for 6.2 from Yuan Can
Thanks,
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 ad8fce3e08cd..e4de649b6701 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\n");
>
> - return ret;
> - }
> ret = regulator_bulk_enable(ARRAY_SIZE(data->regulators),
> data->regulators);
> if (ret) {
prev parent reply other threads:[~2022-10-02 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 6:44 [PATCH -next] iio: accel: bma400: Switch to use dev_err_probe() helper Yang Yingliang
2022-10-02 12:30 ` 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=20221002133046.31d536f0@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan@dlrobertson.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=yangyingliang@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