On 22 February 2013 05:05, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > Why don't you use different values here? > > If you need only one value, one #define should be sufficient. This is the fixup i have for this, I will push all patches again to cpufreq-for-3.10 branch: ---------------------------------------------- commit 4d7296fb64f2353aafad5104f0a046466d0f4ea9 Author: Viresh Kumar <viresh.kumar@xxxxxxxxxx> Date: Fri Feb 22 07:56:31 2013 +0530 fixup! cpufreq: Add per policy governor-init/exit infrastructure --- include/linux/cpufreq.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h index 3b822ce..b7393b5 100644 --- a/include/linux/cpufreq.h +++ b/include/linux/cpufreq.h @@ -183,7 +183,7 @@ static inline unsigned long cpufreq_scale(unsigned long old, u_int div, u_int mu #define CPUFREQ_GOV_STOP 2 #define CPUFREQ_GOV_LIMITS 3 #define CPUFREQ_GOV_POLICY_INIT 4 -#define CPUFREQ_GOV_POLICY_EXIT 4 +#define CPUFREQ_GOV_POLICY_EXIT 5 struct cpufreq_governor { char name[CPUFREQ_NAME_LEN]; -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html