On 10 January 2013 13:24, Shawn Guo <shawn.guo@xxxxxxxxxx> wrote: > On Wed, Jan 09, 2013 at 04:50:44PM +0530, Viresh Kumar wrote: >> @Shawn: I believe your driver don't require that ugly code anymore (Though i >> know there is a situation for that to happen, if we have two cpus, you remove >> second one and then add it back. With this cpufreq_add_dev() would call init() >> first and then try to match if there are any managed_policies present. But the >> issue you pointed out about unregistering the driver would be solved by this >> patch.) > > Yes, just played it and it works for me. However, I would have to keep > that little ugly code in my patch to save the dependency on your patch. > Will send a follow-up to clean that up once your patch hits mainline. Another thing, can i have a tested-by from you for both my patches ? remove and add dev? That would help it go quicker. -- 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
