From: Fabio Cesari <fabio.cesari@gmail.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Brian Masney" <bmasney@redhat.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: light: isl29028: fix runtime PM reference leak on error paths
Date: Mon, 7 Sep 2026 00:09:24 +0200 [thread overview]
Message-ID: <20260906220924.198829-1-fabio.cesari@gmail.com> (raw)
In-Reply-To: <20260906155532.35326455@systembl0wer>
Hi Joshua,
On Sun, 6 Sep 2026 15:55:32 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> I'd put this paragraph under the --- as the Assisted-by tag already mentions
> coccinelle.
Agreed.
> The standard is to use "Assisted-by: LLM coccinelle" to prevent free
> advertising of models.
You're right, that is the form coding-assistants.rst asks for. Fixed.
> I'd suggest rewriting the driver to use the
> PM_RUNTIME_ACQUIRE_IF_ENABLED_AUTOSUSPEND macro, as it automatically
> increments the refcount on use and decrements the refcount on scope exit,
> eliminating the need for multiple _put_autosuspend() calls and manual
> checking of the return value of these calls.
Agreed: the leak cannot be reintroduced by a future error path, and the
return value stops reaching userspace. Both functions use it in v2.
Thanks for the review and the suggestion.
v2 follows shortly; I'll add a Suggested-by.
Fabio
next prev parent reply other threads:[~2026-09-06 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 13:11 [PATCH] iio: light: isl29028: fix runtime PM reference leak on error paths Fabio Cesari
2026-09-06 13:55 ` Joshua Crofts
2026-09-06 22:09 ` Fabio Cesari [this message]
2026-09-06 17:43 ` Jonathan Cameron
2026-09-06 22:15 ` Fabio Cesari
2026-09-07 2:07 ` Jonathan Cameron
2026-09-07 7:29 ` Joshua Crofts
2026-09-09 16:21 ` Fabio Cesari
2026-09-06 22:37 ` [PATCH v2] " Fabio Cesari
2026-09-07 7:19 ` Joshua Crofts
2026-09-07 11:02 ` Fabio Cesari
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=20260906220924.198829-1-fabio.cesari@gmail.com \
--to=fabio.cesari@gmail.com \
--cc=andy@kernel.org \
--cc=bmasney@redhat.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.