From: Jonathan Cameron <jic23@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: "Remi Buisson" <remi.buisson@tdk.com>,
"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,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH next] iio: imu: inv_icm45600: Add a missing return statement in probe()
Date: Mon, 27 Oct 2025 14:23:31 +0000 [thread overview]
Message-ID: <20251027142331.29725dfe@jic23-huawei> (raw)
In-Reply-To: <aPi5vEp75jH0imQc@stanley.mountain>
On Wed, 22 Oct 2025 14:02:20 +0300
Dan Carpenter <dan.carpenter@linaro.org> wrote:
> The intention here was clearly to return -ENODEV but the return statement
> was missing. It would result in an off by one read in i3c_chip_info[] on
> the next line. Add the return statement.
>
> Fixes: 1bef24e9007e ("iio: imu: inv_icm45600: add I3C driver for inv_icm45600 driver")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> drivers/iio/imu/inv_icm45600/inv_icm45600_i3c.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/imu/inv_icm45600/inv_icm45600_i3c.c b/drivers/iio/imu/inv_icm45600/inv_icm45600_i3c.c
> index b5df06b97d44..9247eae9b3e2 100644
> --- a/drivers/iio/imu/inv_icm45600/inv_icm45600_i3c.c
> +++ b/drivers/iio/imu/inv_icm45600/inv_icm45600_i3c.c
> @@ -57,7 +57,8 @@ static int inv_icm45600_i3c_probe(struct i3c_device *i3cdev)
> }
>
> if (chip == nb_chip)
> - dev_err_probe(&i3cdev->dev, -ENODEV, "Failed to match part id %d\n", whoami);
> + return dev_err_probe(&i3cdev->dev, -ENODEV,
> + "Failed to match part id %d\n", whoami);
>
> return inv_icm45600_core_probe(regmap, i3c_chip_info[chip], false, NULL);
> }
I'm going to apply this but the resulting code is still wrong (even if not
a true bug after this fix).
A hard ID match like this breaks use of dt fallback compatibles.
What this should do is 'give it a go' on matching, but if there no match it should
carry on as if the match was to whatever the compatible that was supplied was.
When that happens a dev_info() is appropriate but not error out as this does.
Remi, if possible could you look at adding such a patch on top of this?
Thanks,
Jonathan
next prev parent reply other threads:[~2025-10-27 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 11:02 [PATCH next] iio: imu: inv_icm45600: Add a missing return statement in probe() Dan Carpenter
2025-10-22 15:13 ` David Lechner
2025-10-27 14:23 ` Jonathan Cameron [this message]
2025-10-31 9:56 ` Remi Buisson
2025-11-02 12:15 ` 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=20251027142331.29725dfe@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dlechner@baylibre.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=remi.buisson@tdk.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