[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYnh1IjCfeZz7BH-@smile.fi.intel.com>
Date: Mon, 9 Feb 2026 15:32:04 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@...log.com>
Cc: Linus Walleij <linusw@...nel.org>, Jonathan Cameron <jic23@...nel.org>,
David Lechner <dlechner@...libre.com>,
"Sa, Nuno" <Nuno.Sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] iio: gyro: mpu3050: fix pm_runtime error handling
On Mon, Feb 09, 2026 at 12:13:28PM +0000, Miclaus, Antoniu wrote:
> > -----Original Message-----
> > From: Antoniu Miclaus <antoniu.miclaus@...log.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
Powered by blists - more mailing lists