Re: "cpufreq: fix serialization issues with freq change notifiers"breaks cpufreq too

[Viresh Kumar]

On 10 September 2013 22:37, Guennadi Liakhovetski <g.liakhovetski@xxxxxx> wrote:
> On Tue, 10 Sep 2013, Viresh Kumar wrote:
>> Quite straight forward actually..
>
> Apparently, not quite.

I overlooked the situation where we return early from ->target() routines.. :(

Please try attached patches, I will repost them later (once I am able to
convince Rafael that these are really important :) )

--
viresh

Attachment: 0001-cpufreq-distinguish-drivers-that-do-asynchronous-not.patch
Description: Binary data

Attachment: 0002-cpufreq-fix-notification-serialization-issues.patch
Description: Binary data