From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jean Delvare <jdelvare@suse.com>, Andi Shyti <andi.shyti@kernel.org>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table
Date: Fri, 23 Feb 2024 08:52:23 +0100 [thread overview]
Message-ID: <7e6f4711-5c74-4b82-a136-d3cf19f61593@gmail.com> (raw)
In-Reply-To: <39f39c4e-b997-4698-8406-4d514a530d0d@gmail.com>
On 23.02.2024 08:11, Heiner Kallweit wrote:
> If registering the platform device fails, the lookup table is
> removed in the error path. On module removal we would try to
> remove the lookup table again. Fix this by leaving it to
> i801_del_mux() to clean up.
>
> Fixes: d308dfbf62ef ("i2c: mux/i801: Switch to use descriptor passing")
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/i2c/busses/i2c-i801.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
> index 4b9d04f20..223cd2b84 100644
> --- a/drivers/i2c/busses/i2c-i801.c
> +++ b/drivers/i2c/busses/i2c-i801.c
> @@ -1457,10 +1457,8 @@ static void i801_add_mux(struct i801_priv *priv)
> priv->mux_pdev = platform_device_register_data(dev, "i2c-mux-gpio",
> PLATFORM_DEVID_NONE, &gpio_data,
> sizeof(struct i2c_mux_gpio_platform_data));
> - if (IS_ERR(priv->mux_pdev)) {
> - gpiod_remove_lookup_table(lookup);
> + if (IS_ERR(priv->mux_pdev))
> dev_err(dev, "Failed to register i2c-mux-gpio device\n");
> - }
> }
>
> static void i801_del_mux(struct i801_priv *priv)
Forgot to cc stable in both patches. I'll wait for other feedback and will
submit a v2 afterwards.
prev parent reply other threads:[~2024-02-23 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 7:11 [PATCH] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table Heiner Kallweit
2024-02-23 7:52 ` Heiner Kallweit [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=7e6f4711-5c74-4b82-a136-d3cf19f61593@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@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