From: Jonathan Cameron <jic23@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: <linux-iio@vger.kernel.org>, <peda@axentia.se>, <lars@metafoo.de>,
<Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH -next] iio: multiplexer: Switch to use dev_err_probe() helper
Date: Sun, 2 Oct 2022 13:48:10 +0100 [thread overview]
Message-ID: <20221002134810.02d1c9ed@jic23-huawei> (raw)
In-Reply-To: <20220927064841.319291-1-yangyingliang@huawei.com>
On Tue, 27 Sep 2022 14:48:41 +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>
Applied to the togreg branch of iio.git. Now 6.2 material so I won't push
that branch out until I can rebase on 6.1-rc1
Jonathan
> ---
> drivers/iio/multiplexer/iio-mux.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iio/multiplexer/iio-mux.c b/drivers/iio/multiplexer/iio-mux.c
> index 93558fddfa9b..edd8c69f6d2e 100644
> --- a/drivers/iio/multiplexer/iio-mux.c
> +++ b/drivers/iio/multiplexer/iio-mux.c
> @@ -416,11 +416,9 @@ static int mux_probe(struct platform_device *pdev)
> }
>
> mux->control = devm_mux_control_get(dev, NULL);
> - if (IS_ERR(mux->control)) {
> - if (PTR_ERR(mux->control) != -EPROBE_DEFER)
> - dev_err(dev, "failed to get control-mux\n");
> - return PTR_ERR(mux->control);
> - }
> + if (IS_ERR(mux->control))
> + return dev_err_probe(dev, PTR_ERR(mux->control),
> + "failed to get control-mux\n");
>
> i = 0;
> for (state = 0; state < all_children; state++) {
prev parent reply other threads:[~2022-10-02 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 6:48 [PATCH -next] iio: multiplexer: Switch to use dev_err_probe() helper Yang Yingliang
2022-10-02 12:48 ` 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=20221002134810.02d1c9ed@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=peda@axentia.se \
--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;
as well as URLs for NNTP newsgroup(s).