On Wednesday, November 27, 2013 08:31:02 AM Viresh Kumar wrote: > On 27 November 2013 01:51, Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote: > > I was talking about the case when your > > > > __cpufreq_driver_target(policy, policy->cur - 1, CPUFREQ_RELATION_L); > > > > fails. The other case is not really interesting. > > Okay.. I actually thought the context of this chat is about "not fixing the > frequency silently". That's what Dirk pointed out, if I am not wrong. In that case you can simply print a message bashing the boot loader. :-) > And hence I also support the new pr_warn I have added in those cases. Sure. > But yes a WARN_ON() can be printed out in case > __cpufreq_driver_target() fails. And here my question was: Is it safe to continue at all in that case? Rafael -- 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
