From: Patrick Bellasi <patrick.bellasi@arm.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <juri.lelli@redhat.com>,
Joel Fernandes <joelaf@google.com>
Subject: [PATCH v4 0/2] Fix and cleanup iowait boost
Date: Tue, 22 May 2018 12:07:52 +0100 [thread overview]
Message-ID: <20180522110754.20832-1-patrick.bellasi@arm.com> (raw)
Here is the (hopefully) final update of:
https://lkml.org/lkml/2018/5/21/114
20180521085120.7902-1-patrick.bellasi@arm.com
which just includes the small typo fixes suggested by Jeol and the ack
and review tags collected so far.
Cheers Patrick
Changes in v4:
- fixed typos in changelog (Joel)
- added Reviewed-by Joel Fernandes
- added Acked-by Viresh and Peter
Changes in v3:
- renamed the iowait boost functions (Peter)
- moved boost reset into a dedicated function (Peter)
- split the fix into a separated patch (Viresh)
- added "Fixes" tag (Viresh)
Patrick Bellasi (2):
cpufreq: schedutil: Fix iowait boost reset
cpufreq: schedutil: Cleanup and document iowait boost
kernel/sched/cpufreq_schedutil.c | 152 +++++++++++++++++++++++++++------------
1 file changed, 108 insertions(+), 44 deletions(-)
--
2.15.1
next reply other threads:[~2018-05-22 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 11:07 Patrick Bellasi [this message]
2018-05-22 11:07 ` [PATCH v4 1/2] cpufreq: schedutil: Fix iowait boost reset Patrick Bellasi
2018-05-22 11:07 ` [PATCH v4 2/2] cpufreq: schedutil: Cleanup and document iowait boost Patrick Bellasi
2018-05-23 11:37 ` [PATCH v4 0/2] Fix and cleanup " Rafael J. Wysocki
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=20180522110754.20832-1-patrick.bellasi@arm.com \
--to=patrick.bellasi@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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