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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <10707470.yIcqGAzuFY@vostro.rjw.lan>
Date:	Sat, 14 May 2016 00:58:37 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Linux PM list <linux-pm@...r.kernel.org>
Cc:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events

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