From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.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 v4 0/2] iio: gyro: mpu3050: fix pm_runtime error handling
Date: Fri, 20 Feb 2026 10:59:00 +0000 [thread overview]
Message-ID: <20260220105900.3932c1dc@jic23-huawei> (raw)
In-Reply-To: <cover.1771233915.git.antoniu.miclaus@analog.com>
On Mon, 16 Feb 2026 11:57:54 +0200
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Fix pm_runtime error handling across the mpu3050 driver. The existing
> code uses pm_runtime_get_sync() without checking return values, allowing
> operations to proceed even when the device fails to resume.
>
> Replace pm_runtime_get_sync() with pm_runtime_resume_and_get() and
> propagate errors appropriately. Unlike pm_runtime_get_sync(), the usage
> count is not incremented on error.
Applied to the fixes-togreg branch of iio.git and marked for
stable. Thanks
Jonathan
>
> Changes in v4:
> - Reword commit messages to correctly attribute the unchecked return
> value to the caller rather than pm_runtime_get_sync() itself
> - Simplify preenable by collapsing the trailing return statements
>
> Antoniu Miclaus (2):
> iio: gyro: mpu3050-i2c: fix pm_runtime error handling
> iio: gyro: mpu3050-core: fix pm_runtime error handling
>
> drivers/iio/gyro/mpu3050-core.c | 18 +++++++++++++-----
> drivers/iio/gyro/mpu3050-i2c.c | 3 +--
> 2 files changed, 14 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2026-02-20 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 9:57 [PATCH v4 0/2] iio: gyro: mpu3050: fix pm_runtime error handling Antoniu Miclaus
2026-02-16 9:57 ` [PATCH v4 1/2] iio: gyro: mpu3050-i2c: " Antoniu Miclaus
2026-02-16 9:57 ` [PATCH v4 2/2] iio: gyro: mpu3050-core: " Antoniu Miclaus
2026-02-20 10:59 ` 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=20260220105900.3932c1dc@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.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