From: Jonathan Cameron <jic23@kernel.org>
To: Yang Yingliang <yangyingliang@huaweicloud.com>
Cc: nuno.sa@analog.com, olivier.moysan@foss.st.com, lars@metafoo.de,
linux-iio@vger.kernel.org, yangyingliang@huawei.com,
bobo.shaobowang@huawei.com, Jonathan.Cameron@huawei.com
Subject: Re: [PATCH] iio: backend: fix wrong pointer passed to IS_ERR()
Date: Mon, 28 Oct 2024 20:36:28 +0000 [thread overview]
Message-ID: <20241028203628.2b76cf5a@jic23-huawei> (raw)
In-Reply-To: <20241028135215.1549-1-yangyingliang@huaweicloud.com>
On Mon, 28 Oct 2024 21:52:15 +0800
Yang Yingliang <yangyingliang@huaweicloud.com> wrote:
> From: Yang Yingliang <yangyingliang@huawei.com>
>
> It should be fwnode_back passed to IS_ERR().
>
> Fixes: c464cc610f51 ("iio: add child nodes support in iio backend framework")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Thanks.
Applied to the fixes-togreg branch of iio.git.
I'm not sure if I'll get another fixes pull out due to some upcoming travel,
but if not I'll queue this up for the merge window instead.
Jonathan
> ---
> drivers/iio/industrialio-backend.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-backend.c
> index 20b3b5212da7..fb34a8e4d04e 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -737,8 +737,8 @@ static struct iio_backend *__devm_iio_backend_fwnode_get(struct device *dev, con
> }
>
> fwnode_back = fwnode_find_reference(fwnode, "io-backends", index);
> - if (IS_ERR(fwnode))
> - return dev_err_cast_probe(dev, fwnode,
> + if (IS_ERR(fwnode_back))
> + return dev_err_cast_probe(dev, fwnode_back,
> "Cannot get Firmware reference\n");
>
> guard(mutex)(&iio_back_lock);
prev parent reply other threads:[~2024-10-28 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 13:52 [PATCH] iio: backend: fix wrong pointer passed to IS_ERR() Yang Yingliang
2024-10-28 20:36 ` 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=20241028203628.2b76cf5a@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=bobo.shaobowang@huawei.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=yangyingliang@huawei.com \
--cc=yangyingliang@huaweicloud.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