From: Jonathan Cameron <jic23@kernel.org>
To: Stepan Ionichev <sozdayvek@gmail.com>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
hcazarim@yahoo.com, joshua.crofts1@gmail.com,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] iio: light: tsl2591: return actual error from probe IRQ failure
Date: Mon, 18 May 2026 16:40:48 +0100 [thread overview]
Message-ID: <20260518163647.3b4966fb@jic23-huawei> (raw)
In-Reply-To: <20260518094311.2000-1-sozdayvek@gmail.com>
On Mon, 18 May 2026 14:43:11 +0500
Stepan Ionichev <sozdayvek@gmail.com> wrote:
> When devm_request_threaded_irq() fails, probe logs the error and
> then returns -EINVAL, dropping the real error code and breaking the
> deferred-probe flow for -EPROBE_DEFER.
>
> Return ret directly; the IRQ subsystem already prints on failure.
>
> Fixes: 2335f0d7c790 ("iio: light: Added AMS tsl2591 driver implementation")
Hmm. To me borderline on whether it's a fix. In theory a board may exist
where the defer is a possibility. In practice probably not given I don't
think we've ever had a report of this.
Meh, it's harmless enough and maybe helps someone.
> Cc: stable@vger.kernel.org
> Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
New series versions should never be in reply to older series.
It tends to hide them in people's inboxes and brings little nor no benefit.
> ---
> v2:
> - Drop dev_err_probe(); just return ret (Andy)
> - Add Cc: stable@ as suggested by Joshua
Mostly for IIO I add those to patches that I think need it but don't object
if people feel strongly enough and add them themselves.
Applied to the iio-fixes branch of iio.git.
>
> v1: https://lore.kernel.org/all/20260517181042.668-1-sozdayvek@gmail.com/
>
> drivers/iio/light/tsl2591.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/light/tsl2591.c b/drivers/iio/light/tsl2591.c
> index c5557867e..c5ccd833d 100644
> --- a/drivers/iio/light/tsl2591.c
> +++ b/drivers/iio/light/tsl2591.c
> @@ -1137,10 +1137,8 @@ static int tsl2591_probe(struct i2c_client *client)
> NULL, tsl2591_event_handler,
> IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> "tsl2591_irq", indio_dev);
> - if (ret) {
> - dev_err_probe(&client->dev, ret, "IRQ request error\n");
> - return -EINVAL;
> - }
> + if (ret)
> + return ret;
> indio_dev->info = &tsl2591_info;
> } else {
> indio_dev->info = &tsl2591_info_no_irq;
next prev parent reply other threads:[~2026-05-18 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 18:10 [PATCH] iio: light: tsl2591: return actual error from probe IRQ failure Stepan Ionichev
2026-05-17 18:25 ` Joshua Crofts
2026-05-18 7:37 ` Andy Shevchenko
2026-05-18 9:43 ` [PATCH v2] " Stepan Ionichev
2026-05-18 15:40 ` Jonathan Cameron [this message]
2026-05-18 15:43 ` Jonathan Cameron
2026-06-03 17:23 ` Jonathan Cameron
2026-06-04 7:25 ` Andy Shevchenko
2026-06-04 7:26 ` Andy Shevchenko
2026-07-03 19:10 ` Jonathan Cameron
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=20260518163647.3b4966fb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=hcazarim@yahoo.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sozdayvek@gmail.com \
--cc=stable@vger.kernel.org \
/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