From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com>
Cc: Linus Walleij <linusw@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
David Lechner <dlechner@baylibre.com>,
"Sa, Nuno" <Nuno.Sa@analog.com>,
Andy Shevchenko <andy@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] iio: gyro: mpu3050: fix pm_runtime error handling
Date: Mon, 9 Feb 2026 15:32:04 +0200 [thread overview]
Message-ID: <aYnh1IjCfeZz7BH-@smile.fi.intel.com> (raw)
In-Reply-To: <CY4PR03MB33997BF46685A6E43BF40EAA9B65A@CY4PR03MB3399.namprd03.prod.outlook.com>
On Mon, Feb 09, 2026 at 12:13:28PM +0000, Miclaus, Antoniu wrote:
> > -----Original Message-----
> > From: Antoniu Miclaus <antoniu.miclaus@analog.com>
> > Sent: Monday, February 9, 2026 1:33 PM
> > 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.
> >
> > Changes in v3:
> > - Rename patches to focus on fix rather than API change
> > - Add Fixes: tags
> > - Collect Reviewed-by
>
> Sent by mistake, only the cover-letter. This patch can be ignored.
You lost me. Did you send the cover-letter by a mistake, or
the entire series? "This patch" is absent in the cover letter
and for the matter of fact, there are two patches in it.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-09 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 11:33 [PATCH v3 0/2] iio: gyro: mpu3050: fix pm_runtime error handling Antoniu Miclaus
2026-02-09 12:02 ` Antoniu Miclaus
2026-02-09 12:02 ` [PATCH v3 1/2] iio: gyro: mpu3050-i2c: " Antoniu Miclaus
2026-02-09 12:02 ` [PATCH v3 2/2] iio: gyro: mpu3050-core: " Antoniu Miclaus
2026-02-09 13:34 ` Andy Shevchenko
2026-02-09 14:27 ` Nuno Sá
2026-02-09 12:13 ` [PATCH v3 0/2] iio: gyro: mpu3050: " Miclaus, Antoniu
2026-02-09 13:32 ` Andy Shevchenko [this message]
2026-02-09 13:39 ` Miclaus, Antoniu
2026-02-09 13:54 ` Andy Shevchenko
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=aYnh1IjCfeZz7BH-@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Antoniu.Miclaus@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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