Linux-i2c Archive mirror
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Jean Delvare <jdelvare@suse.com>, Wolfram Sang <wsa@kernel.org>,
	 Heiner Kallweit <hkallweit1@gmail.com>
Cc: linux-i2c@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v3] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table
Date: Wed, 06 Mar 2024 12:55:26 +0100	[thread overview]
Message-ID: <170972612682.1712532.1072474863479883972.b4-ty@kernel.org> (raw)
In-Reply-To: <8d35529d-8ba9-4bdd-a3a3-00d67ab6f2d5@gmail.com>

Hi

On Mon, 04 Mar 2024 21:31:06 +0100, 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 setting priv->lookup
> only if registering the platform device was successful.
> In addition free the memory allocated for the lookup table in
> the error path.
> 
> [...]

Applied to i2c/i2c-host-fixes on

git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

Thank you,
Andi

Patches applied
===============
[1/1] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table
      commit: 7c16cfd69d519ba14c9e9d474facd22d075ad14d


      parent reply	other threads:[~2024-03-06 12:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 20:31 [PATCH v3] i2c: i801: Avoid potential double call to gpiod_remove_lookup_table Heiner Kallweit
2024-03-04 23:04 ` Andi Shyti
2024-03-05  7:06   ` Heiner Kallweit
2024-03-05  8:54 ` Linus Walleij
2024-03-05  9:48   ` [SPAM] " Andi Shyti
2024-03-06 11:55 ` Andi Shyti [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=170972612682.1712532.1072474863479883972.b4-ty@kernel.org \
    --to=andi.shyti@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).