Linux Power Management development
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: 'Giovanni Gherdovich' <ggherdovich@suse.cz>,
	'Srinivas Pandruvada' <srinivas.pandruvada@linux.intel.com>,
	'Peter Zijlstra' <peterz@infradead.org>,
	'LKML' <linux-kernel@vger.kernel.org>,
	'Frederic Weisbecker' <frederic@kernel.org>,
	'Mel Gorman' <mgorman@suse.de>,
	'Daniel Lezcano' <daniel.lezcano@linaro.org>,
	"'Chen, Hu'" <hu1.chen@intel.com>,
	'Quentin Perret' <quentin.perret@arm.com>,
	'Linux PM' <linux-pm@vger.kernel.org>,
	Doug Smythies <dsmythies@telus.net>
Subject: RE: [PATCH] cpuidle: New timer events oriented governor for tickless systems
Date: Tue, 18 Dec 2018 07:32:33 -0800	[thread overview]
Message-ID: <000001d496e6$e968c8f0$bc3a5ad0$@net> (raw)
In-Reply-To: ZDGBgBJlZBdpLZDGGgQX53

Hi Rafael,

Just typos, not already pointed out by Quentin:

On 2018.12.18 03:09 Rafael J. Wysocki wrote:

> The venerable menu governor does some thigns that are quite

s/thigns/things

> time frame in which no timer wakeups are possible (becuase it knows

s/because/because

> +obtain the the *sleep length*, which is the time until the closest timer event

s/the the/the

> +increased when when the given idle state "matches" the sleep length only and the

s/when when/when

... Doug

             reply	other threads:[~2018-12-18 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 15:32 Doug Smythies [this message]
2018-12-18 15:38 ` [PATCH] cpuidle: New timer events oriented governor for tickless systems Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2018-12-18 11:09 Rafael J. Wysocki
2018-12-18 11:49 ` Quentin Perret
2018-12-18 15:31   ` Rafael J. Wysocki
2018-12-19  9:32     ` Quentin Perret

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='000001d496e6$e968c8f0$bc3a5ad0$@net' \
    --to=dsmythies@telus.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=frederic@kernel.org \
    --cc=ggherdovich@suse.cz \
    --cc=hu1.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=quentin.perret@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@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