From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC] PM / Domains: Minimize latencies by not delaying save/restore
Date: Mon, 11 May 2015 10:00:09 -0700 [thread overview]
Message-ID: <7hbnhrdp7q.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1431350673-871-1-git-send-email-ulf.hansson@linaro.org> (Ulf Hansson's message of "Mon, 11 May 2015 15:24:33 +0200")
Ulf Hansson <ulf.hansson@linaro.org> writes:
[...]
> To address these two issues, let's change the policy in genpd. More
> precisely, let's walk the hierarchy of the ->runtime_suspend()
> callbacks immediately when genpd's ->runtime_suspend() callback at the
> PM domain level is invoked.
To help in understanding this change, you might also consider leading
with something like this paragraph. IOW, start with an intro pargraph
about *what* you are changing, and then go into the why.
The current changlog goes into great detail about "why" before ever
explaining the "what".
Kevin
prev parent reply other threads:[~2015-05-11 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 13:24 [PATCH/RFC] PM / Domains: Minimize latencies by not delaying save/restore Ulf Hansson
2015-05-11 14:41 ` Russell King - ARM Linux
2015-05-11 17:00 ` Kevin Hilman [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=7hbnhrdp7q.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).