mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, gregkh@linuxfoundation.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] iio: temperature: tmp006: use devm_iio_trigger_register
Date: Mon, 18 May 2026 16:47:21 +0100	[thread overview]
Message-ID: <20260518164721.73fcc8c7@jic23-huawei> (raw)
In-Reply-To: <20260517182614.218-1-sozdayvek@gmail.com>

On Sun, 17 May 2026 23:26:13 +0500
Stepan Ionichev <sozdayvek@gmail.com> wrote:

> tmp006_probe() allocates the DRDY trigger with devm_iio_trigger_alloc()
> but registers it with plain iio_trigger_register(). The driver has no
> .remove() callback, so on module unload the trigger stays in the global
> trigger list while its memory is freed by devm, leaving a dangling
> entry.
> 
> Switch to devm_iio_trigger_register() so the registration is undone in
> the same devm scope as the allocation.
> 
> Fixes: 91f75ccf9f03 ("iio: temperature: tmp006: add triggered buffer support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
Looks 'obviously' correct enough that I'll pick it up with the very little time
it's been on list.  If anyone disagrees do shout!

Applied to the fixes-togreg branch of iio.git

Thanks

Jonathan

> ---
>  drivers/iio/temperature/tmp006.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/temperature/tmp006.c b/drivers/iio/temperature/tmp006.c
> index d8d8c8936..bf62143fa 100644
> --- a/drivers/iio/temperature/tmp006.c
> +++ b/drivers/iio/temperature/tmp006.c
> @@ -350,7 +350,7 @@ static int tmp006_probe(struct i2c_client *client)
>  
>  		data->drdy_trig->ops = &tmp006_trigger_ops;
>  		iio_trigger_set_drvdata(data->drdy_trig, indio_dev);
> -		ret = iio_trigger_register(data->drdy_trig);
> +		ret = devm_iio_trigger_register(&client->dev, data->drdy_trig);
>  		if (ret)
>  			return ret;
>  


      reply	other threads:[~2026-05-18 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 18:26 Stepan Ionichev
2026-05-18 15:47 ` 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=20260518164721.73fcc8c7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hcazarim@yahoo.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

all inboxes | Powered by JetHome®