On 08-07-15, 12:17, Jon Medhurst (Tixy) wrote: > I tried these patches without the earlier "cpufreq: Initialize the > governor again while restoring policy" patch. > > The result is that the error when bringing a cpu online is with flagged > up with a kernel message: > > cpufreq: cpufreq_add_dev: Failed to initialize policy for cpu: 1 (-16) > > and afterwards, the sysfs entries that I was poking and causing the > crash aren't present. So looks like this patch has done what we want, > and cleaned things up after an error. So... > > Tested-by: Jon Medhurst <[email protected]> > > Thanks for the prompt fix.
And thanks for your help in getting these tested :) -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
