From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 08/51] gpio: Switch to __pm_runtime_put_autosuspend()
Date: Fri, 4 Oct 2024 11:55:01 +0200 [thread overview]
Message-ID: <CAMRc=Mfx+OagrGPkMw2LFu_Yzu4cpDnCQPVA3C3rJarCBGE_bw@mail.gmail.com> (raw)
In-Reply-To: <20241004094112.113487-1-sakari.ailus@linux.intel.com>
On Fri, Oct 4, 2024 at 11:41 AM Sakari Ailus
<sakari.ailus@linux.intel.com> wrote:
>
> pm_runtime_put_autosuspend() will soon be changed to include a call to
> pm_runtime_mark_last_busy(). This patch switches the current users to
> __pm_runtime_put_autosuspend() which will continue to have the
> functionality of old pm_runtime_put_autosuspend().
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
Sakari,
You didn't Cc me on the cover letter, please do it next time whenever
you post such a big series.
I got the cover letter from lore but it doesn't explain how this will
be merged, are there prerequisites earlier in the series? Or are the
patches independent? If the latter, why not send them separately
targeting individual subsystems?
Bart
next prev parent reply other threads:[~2024-10-04 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:41 [PATCH 00/51] treewide: Switch to __pm_runtime_put_autosuspend() Sakari Ailus
2024-10-04 9:41 ` [PATCH 08/51] gpio: " Sakari Ailus
2024-10-04 9:55 ` Bartosz Golaszewski [this message]
2024-10-04 10:08 ` Sakari Ailus
2024-10-04 14:38 ` [PATCH 00/51] treewide: " Ulf Hansson
2024-10-07 18:49 ` Laurent Pinchart
2024-10-07 22:08 ` Ulf Hansson
2024-10-07 22:25 ` Laurent Pinchart
2024-10-07 22:34 ` Ulf Hansson
2024-10-08 18:24 ` Rafael J. Wysocki
2024-10-09 10:20 ` Rafael J. Wysocki
2024-10-09 10:27 ` Ulf Hansson
2024-10-09 12:48 ` Richard Fitzgerald
2024-10-09 13:34 ` Rafael J. Wysocki
2024-10-08 20:38 ` Uwe Kleine-König
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='CAMRc=Mfx+OagrGPkMw2LFu_Yzu4cpDnCQPVA3C3rJarCBGE_bw@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).