[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 3 Mar 2016 11:33:21 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Linux PM list <linux-pm@...r.kernel.org>,
Juri Lelli <juri.lelli@....com>,
Steve Muckle <steve.muckle@...aro.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Michael Turquette <mturquette@...libre.com>
Subject: Re: [PATCH 4/6] cpufreq: governor: Move abstract gov_tunables code
to a seperate file
On 02-03-16, 03:10, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
>
> Move abstract code related to struct gov_tunables to a separate (new)
> file so it can be shared with (future) goverernors that won't share
> more code with "ondemand" and "conservative".
>
> No intentional functional changes.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> ---
> drivers/cpufreq/Kconfig | 4 +
> drivers/cpufreq/Makefile | 1
> drivers/cpufreq/cpufreq_governor.c | 82 ---------------------------
> drivers/cpufreq/cpufreq_governor.h | 6 ++
> drivers/cpufreq/cpufreq_governor_tunables.c | 84 ++++++++++++++++++++++++++++
These aren't governor tunables, isn't it? Tunables were the fields
that could be tuned, but this is something else.
--
viresh
Powered by blists - more mailing lists