From: Jonathan Cameron <jic23@kernel.org>
To: Salah Triki <salah.triki@gmail.com>
Cc: "Andreas Klinger" <ak@it-klinger.de>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: proximity: srf04: fix error handling in srf04_probe()
Date: Thu, 20 Aug 2026 02:58:29 +0100 [thread overview]
Message-ID: <20260820025829.7a2ae2b4@jic23-huawei> (raw)
In-Reply-To: <20260819190317.8745-1-salah.triki@gmail.com>
On Wed, 19 Aug 2026 20:03:17 +0100
Salah Triki <salah.triki@gmail.com> wrote:
> If pm_runtime_set_active() fails during srf04_probe(),
> iio_device_unregister() is called to cleanup, but the driver continues to
> execute pm_runtime_enable() and pm_runtime_idle() instead of aborting
> probe.
>
> Fix this by returning 'ret' immediately inside the error path if
> pm_runtime_set_active() fails, preventing invalid runtime PM operations on
> an unregistered device.
>
> Fixes: 2251157b335b ("iio: srf04: add power management feature")
> Signed-off-by: Salah Triki <salah.triki@gmail.com>
Fixed a few weeks back.
Thanks
Jonathan
> ---
> drivers/iio/proximity/srf04.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/proximity/srf04.c b/drivers/iio/proximity/srf04.c
> index 7be50bdebfcb..e03f3f0dee04 100644
> --- a/drivers/iio/proximity/srf04.c
> +++ b/drivers/iio/proximity/srf04.c
> @@ -330,6 +330,7 @@ static int srf04_probe(struct platform_device *pdev)
> if (ret) {
> dev_err(data->dev, "pm_runtime_set_active: %d\n", ret);
> iio_device_unregister(indio_dev);
> + return ret;
> }
>
> pm_runtime_enable(data->dev);
prev parent reply other threads:[~2026-08-20 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 19:03 Salah Triki
2026-08-20 1:58 ` 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=20260820025829.7a2ae2b4@jic23-huawei \
--to=jic23@kernel.org \
--cc=ak@it-klinger.de \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=salah.triki@gmail.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
all inboxes | Powered by JetHome®