On 28 January 2013 17:56, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > So here's a deal: I'll drop "cpufreq: Simplify cpufreq_add_dev()" for now and > you'll generate a new patch that won't cause the WARN_ON() to trigger. OK? :( Or what about set all cpus from policy->cpus into related_cpus in our core code? So, if platform sets any additional cpus, they would be retained? -- 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
