From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>
Cc: '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>,
'Giovanni Gherdovich' <ggherdovich@suse.cz>,
'Daniel Lezcano' <daniel.lezcano@linaro.org>,
'Linux PM' <linux-pm@vger.kernel.org>,
Doug Smythies <dsmythies@telus.net>
Subject: RE: [RFC/RFT][PATCH v2] cpuidle: New timer events oriented governor for tickless systems
Date: Fri, 26 Oct 2018 23:37:24 -0700 [thread overview]
Message-ID: <001201d46dbf$88339510$989abf30$@net> (raw)
In-Reply-To: FyDdgD8Nty5tHFyDfgBIL9
This is just for anybody else trying to compile:
On 2018.10.26 02:12 Rafael J. Wysocki wrote:
> The venerable menu governor does some thigns that are quite
Typo: thigns -> things
...[snip]...
> The patch should apply on top of 4.19, although I'm running it on
> top of my linux-next branch.
No, it uses "poll_time_limit" which was introduced in patch 1 of 6
[1] in that group of menu changes from October 2nd.
"[PATCH 1/6] cpuidle: menu: Fix wakeup statistics updates for polling state"
... Doug
[1] https://lkml.org/lkml/2018/10/3/42
next reply other threads:[~2018-10-27 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 6:37 Doug Smythies [this message]
2018-10-30 7:19 ` [RFC/RFT][PATCH v2] cpuidle: New timer events oriented governor for tickless systems Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2018-11-02 15:39 Doug Smythies
2018-11-04 10:06 ` Rafael J. Wysocki
2018-11-05 19:11 ` Giovanni Gherdovich
2018-11-05 21:28 ` Doug Smythies
2018-10-26 9:12 Rafael J. Wysocki
2018-10-31 18:36 ` Giovanni Gherdovich
2018-11-04 10:06 ` Rafael J. Wysocki
2018-11-05 19:14 ` Giovanni Gherdovich
2018-11-05 22:09 ` Doug Smythies
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='001201d46dbf$88339510$989abf30$@net' \
--to=dsmythies@telus.net \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=ggherdovich@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).