From: "Nuno Sá" <noname.nuno@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
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] iio: gyro: mpu3050-i2c: use pm_runtime_resume_and_get()
Date: Tue, 03 Feb 2026 09:39:55 +0000 [thread overview]
Message-ID: <0b16fc61249b507bb65f3f0f4a9c1e5eef4b41a4.camel@gmail.com> (raw)
In-Reply-To: <20260131164135.35f07a27@jic23-huawei>
On Sat, 2026-01-31 at 16:41 +0000, Jonathan Cameron wrote:
> On Fri, 30 Jan 2026 17:32:26 +0200
> Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
>
> > Use pm_runtime_resume_and_get() in bypass_select() and return its
> > result directly. Unlike pm_runtime_get_sync(), it doesn't increment
> > the refcount on failure.
> >
> > Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
>
> Please always put a cover letter on anything with more than one patch.
> Provides both a nice name for the series in patchwork etc and a
> single place to reply.
>
> Are these fixes? What is side effect of the wrong ref count?
Yeps, at first glance I would count this as a fix...
- Nuno Sá
>
next prev parent reply other threads:[~2026-02-03 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 15:32 Antoniu Miclaus
2026-01-30 15:32 ` [PATCH] iio: gyro: mpu3050-core: " Antoniu Miclaus
2026-02-03 0:21 ` Linus Walleij
2026-01-31 16:41 ` [PATCH] iio: gyro: mpu3050-i2c: " Jonathan Cameron
2026-02-03 9:39 ` Nuno Sá [this message]
2026-02-03 11:13 ` 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=0b16fc61249b507bb65f3f0f4a9c1e5eef4b41a4.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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
all inboxes | Powered by JetHome®