linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yangtao Li <tiny.windzz@gmail.com>
To: rjw@rjwysocki.net, daniel.lezcano@linaro.org, corbet@lwn.net
Cc: linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Yangtao Li <tiny.windzz@gmail.com>
Subject: [PATCH] cpuidle: fix description of exit latency in cpuidle.rst
Date: Tue, 22 Jan 2019 09:06:44 -0500	[thread overview]
Message-ID: <20190122140644.25535-1-tiny.windzz@gmail.com> (raw)

Exit latency is the time from exiting the idle state to execute
the first instruction. This place may be a typo , so fix it.

Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
---
 Documentation/admin-guide/pm/cpuidle.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/admin-guide/pm/cpuidle.rst b/Documentation/admin-guide/pm/cpuidle.rst
index 106379e2619f..3ca2ca60ff91 100644
--- a/Documentation/admin-guide/pm/cpuidle.rst
+++ b/Documentation/admin-guide/pm/cpuidle.rst
@@ -134,7 +134,7 @@ substantial), in order to save more energy than it would save by entering one of
 the shallower idle states instead.  [The "depth" of an idle state roughly
 corresponds to the power drawn by the processor in that state.]  The exit
 latency, in turn, is the maximum time it will take a CPU asking the processor
-hardware to enter an idle state to start executing the first instruction after a
+hardware to exit an idle state to start executing the first instruction after a
 wakeup from that state.  Note that in general the exit latency also must cover
 the time needed to enter the given state in case the wakeup occurs when the
 hardware is entering it and it must be entered completely to be exited in an
-- 
2.17.0


             reply	other threads:[~2019-01-22 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 14:06 Yangtao Li [this message]
2019-01-22 14:39 ` [PATCH] cpuidle: fix description of exit latency in cpuidle.rst Frank Lee

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=20190122140644.25535-1-tiny.windzz@gmail.com \
    --to=tiny.windzz@gmail.com \
    --cc=corbet@lwn.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).