From: Jonathan Cameron <jic23@kernel.org>
To: Biren Pandya <birenpandya@gmail.com>
Cc: "Linus Walleij" <linusw@kernel.org>,
"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
Subject: Re: [PATCH v1 0/4] iio: Fix runtime PM leaks across multiple drivers
Date: Sun, 14 Jun 2026 14:31:09 +0100 [thread overview]
Message-ID: <20260614143109.7e2ba4df@jic23-huawei> (raw)
In-Reply-To: <20260614071549.81920-1-birenpandya@gmail.com>
On Sun, 14 Jun 2026 12:45:45 +0530
Biren Pandya <birenpandya@gmail.com> wrote:
> Hi Jonathan,
>
> While auditing the IIO subsystem, I noticed a recurring pattern in
> several drivers where early returns or error paths fail to drop their
> pm_runtime_get_sync() references. This permanently leaves the device
> active and prevents autosuspension.
>
> This series provides four independent fixes for these imbalances across
> the kxsd9, mpu3050, mpl115, and gp2ap002 drivers.
>
> Because these drivers are independent, these patches do not depend on
> each other and can be merged individually.
Oops. Too me until just after I'd replied to patch 4 to notice
that these don't have the necessary Fixes tags.
I've added them, but keep that in mind for next time you send a fix.
Thanks,
Jonathan
>
> Best regards,
> Biren Pandya
>
>
> drivers/iio/accel/kxsd9.c | 5 +++--
> drivers/iio/gyro/mpu3050-core.c | 16 +++++++++++-----
> drivers/iio/light/gp2ap002.c | 2 +-
> drivers/iio/pressure/mpl115.c | 4 ++--
> 4 files changed, 17 insertions(+), 10 deletions(-)
>
prev parent reply other threads:[~2026-06-14 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 7:15 [PATCH v1 0/4] iio: Fix runtime PM leaks across multiple drivers Biren Pandya
2026-06-14 7:15 ` [PATCH v1 1/4] iio: accel: kxsd9: fix runtime PM imbalance on write_raw() error Biren Pandya
2026-06-14 13:14 ` Jonathan Cameron
2026-06-14 7:15 ` [PATCH v1 2/4] iio: gyro: mpu3050: fix runtime PM leak when enabling trigger fails Biren Pandya
2026-06-14 13:22 ` Jonathan Cameron
2026-06-14 7:15 ` [PATCH v1 3/4] iio: pressure: mpl115: fix runtime PM leak on read error Biren Pandya
2026-06-14 13:24 ` Jonathan Cameron
2026-06-14 7:15 ` [PATCH v1 4/4] iio: light: gp2ap002: " Biren Pandya
2026-06-14 13:25 ` Jonathan Cameron
2026-06-14 13:31 ` 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=20260614143109.7e2ba4df@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=birenpandya@gmail.com \
--cc=dlechner@baylibre.com \
--cc=linusw@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox