On Friday, February 01, 2013 08:08:42 AM Viresh Kumar wrote: > On 1 February 2013 08:01, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > > Really!! I see bleeding edge as df0e3f4 and i don't see the $(subject) patch > > in it :) > > Well it might have been dropped by Rafael due to build error, Precisely. > which would be fixed by: > > diff --git a/drivers/cpufreq/cpufreq_governor.c > b/drivers/cpufreq/cpufreq_governor.c > index dc99472..7aaa9b1 100644 > --- a/drivers/cpufreq/cpufreq_governor.c > +++ b/drivers/cpufreq/cpufreq_governor.c > @@ -194,6 +194,7 @@ bool need_load_eval(struct cpu_dbs_common_info *cdbs, > > return true; > } > +EXPORT_SYMBOL_GPL(need_load_eval); > > int cpufreq_governor_dbs(struct dbs_data *dbs_data, > struct cpufreq_policy *policy, unsigned int event) > > > Original patch attached with this change. OK, thanks! Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- 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
