On 28 January 2013 15:19, Borislav Petkov wrote:
> Which one would you suggest: CPUFREQ DRIVER INTERFACE?
Yes.
> Btw, this function type splitting looks kinda silly to me. In that same
> section there are two which clearly don't belong there:
>
> struct cpufreq_policy *cpufreq_cpu_get(unsigned i
On Mon, Jan 28, 2013 at 10:07:10AM +0530, Viresh Kumar wrote:
> Two minor things here:
> - You placed the routine at bad place. This place is meant for
> freq_table helpers.
Which one would you suggest: CPUFREQ DRIVER INTERFACE?
Btw, this function type splitting looks kinda silly to me. In that s
On Sun, Jan 20, 2013 at 3:54 PM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Add a helper function to return cpufreq_driver->name.
>
> Signed-off-by: Borislav Petkov
> ---
> drivers/cpufreq/cpufreq.c | 14 ++
> include/linux/cpufreq.h | 1 +
> 2 files changed, 15 insertion
From: Borislav Petkov
Add a helper function to return cpufreq_driver->name.
Signed-off-by: Borislav Petkov
---
drivers/cpufreq/cpufreq.c | 14 ++
include/linux/cpufreq.h | 1 +
2 files changed, 15 insertions(+)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
4 matches
Mail list logo