[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2998470.K7oslgfuja@vostro.rjw.lan>
Date: Sun, 07 Feb 2016 16:22:49 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linux PM list <linux-pm@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Juri Lelli <juri.lelli@....com>,
Steve Muckle <steve.muckle@...aro.org>,
Saravana Kannan <skannan@...eaurora.org>
Subject: [PATCH 0/3] cpufreq: governor: Data structure rearrangement
Hi,
This was part of my recent cleanup series
(http://marc.info/?l=linux-pm&m=145463901630950&w=4), but Viresh had a good
point about the patch doing too much and possibly going too far, so I've
reworked it into a series of three smaller patches and dropped some more
aggressive changes.
[1/3] simplifies cpufreq_governor_limits() to access the policy via its
argument directly.
[2/3] rearranges the data structures so policy->governor_data points to the
struct policy_dbs corresponding to that policy and the latter points
to a struct dbs_data.
[3/3] makes the initialization and cleanup of struct cpu_dbs_info more
symmetrical.
Patches are on top of my bleeding-edge branch (and there is a separate
pm-cpufreq-test branch with cpufreq patches only in case someone wants/needs
to test those alone).
Thanks,
Rafael
Powered by blists - more mailing lists