On Monday, October 21, 2013 12:43:32 PM Viresh Kumar wrote: > On 13 October 2013 06:07, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > > On 13/10/2013, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > >> -> What about this: > >> > >> /* > >> * The core will not set policy->cur, because cpufreq_driver->get is NULL, > >> * so we need to set it here. However, we have to guess it, because the > >> * current speed is unknown and not detectable via IO ports. > >> */ > > > > Far better. Attached again. Thanks. > > Have you missed applying this one? Attached again.. I don't think I've missed it. It should be commit 1bab64d in my tree. Thanks! -- 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
