[PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events

From	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Newsgroups	linux.kernel
Subject	[PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events
Date	2016-05-14 01:00 +0200
Message-ID	<ryudP-4h8-3@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi,

This series is on top of the current linux-next witn the following two patches
applied:

https://patchwork.kernel.org/patch/9080801/
https://patchwork.kernel.org/patch/9080791/

It cleans up a few things and then reworks the governor API to get rid of
governor events and use callbacks representing individual governor operations
(init, exit, start, stop, limits update) instead.

I'm regarding it as v4.8 material, but I'd like to put it into linux-next as
soon as 4.7-rc1 is out so subsequent cpufreq development happens on top of it.

It has been lightly tested without any problems showing up so far.

Thanks,
Rafael

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-05-14 01:00 +0200
  [PATCH 2/5] cpufreq: governor: Check transition latecy at init time only "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-05-14 01:00 +0200
  [PATCH 5/5] cpufreq: governor: Get rid of governor events "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-05-14 01:10 +0200
    Re: [PATCH 5/5] cpufreq: governor: Get rid of governor events Viresh Kumar <viresh.kumar@linaro.org> - 2016-05-16 07:00 +0200
  [PATCH 4/5] cpufreq: Split cpufreq_governor() into simpler functions "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-05-14 01:10 +0200
  Re: [PATCH 0/5] cpufreq: governor: Rework API to use callbacks  instead of events Viresh Kumar <viresh.kumar@linaro.org> - 2016-05-16 07:00 +0200

csiph-web