From: Ulf Hansson <ulf.hansson@linaro.org>
To: "Rafael J . Wysocki" <rafael@kernel.org>, linux-pm@vger.kernel.org
Cc: Kevin Hilman <khilman@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Dmitry Osipenko <digetx@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] PM: domains: Some minor improvements for genpd_power_off()
Date: Wed, 4 May 2022 11:35:08 +0200 [thread overview]
Message-ID: <CAPDyKFrxr_t5iCa4E5Obvzk25wQbLCoY2Co=8iG==WfbBhpRVQ@mail.gmail.com> (raw)
In-Reply-To: <20220426141507.89868-1-ulf.hansson@linaro.org>
On Tue, 26 Apr 2022 at 16:15, Ulf Hansson <ulf.hansson@linaro.org> wrote:
>
> This small series intends to improve some of the execution paths when powering
> off a genpd. More information is available in the commit messages.
>
> Ulf Hansson (3):
> PM: domains: Add GENPD_FLAG_RPM_ALWAYS_ON for the always-on governor
> PM: domains: Drop redundant code for genpd always-on governor
> PM: domain: Don't check PM_QOS_FLAG_NO_POWER_OFF in genpd
>
> drivers/base/power/domain.c | 10 ++++------
> drivers/base/power/domain_governor.c | 6 ------
> 2 files changed, 4 insertions(+), 12 deletions(-)
>
Rafael, I have another slew of patches for genpd that I am getting
prepared to submit. However, it would be nice to get @subject series
queued first. Is it ready to go, you think?
Kind regards
Uffe
prev parent reply other threads:[~2022-05-04 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 14:15 [PATCH 0/3] PM: domains: Some minor improvements for genpd_power_off() Ulf Hansson
2022-04-26 14:15 ` [PATCH 1/3] PM: domains: Add GENPD_FLAG_RPM_ALWAYS_ON for the always-on governor Ulf Hansson
2022-04-26 14:15 ` [PATCH 2/3] PM: domains: Drop redundant code for genpd " Ulf Hansson
2022-04-26 14:15 ` [PATCH 3/3] PM: domain: Don't check PM_QOS_FLAG_NO_POWER_OFF in genpd Ulf Hansson
2022-05-04 9:35 ` Ulf Hansson [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='CAPDyKFrxr_t5iCa4E5Obvzk25wQbLCoY2Co=8iG==WfbBhpRVQ@mail.gmail.com' \
--to=ulf.hansson@linaro.org \
--cc=digetx@gmail.com \
--cc=geert@linux-m68k.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).