On Sat, Mar 23, 2013 at 10:34:28PM +0530, Viresh Kumar wrote:
> And that is already caused recently?
3.8.3 is fine and there are no cpufreq patches in v3.8..v3.8.3. Which
would mean, plain v3.8 is also fine. Which means, the breakage must've
come in during the merge window.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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
