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

[Viresh Kumar]

On 12 September 2013 16:31, Rafael J. Wysocki <rjw at rjwysocki.net> wrote:
> Well, if there's more than one it's even simpler.  You can just pick one. :-)
>
> Like, "for example, <driver name> does the following ... which may cause the
> hardware to misbehave, because ...".

:)

I have written one of my longest changelog ever on the resent of this patch..
Hope that doesn't have any unanswered stuff left :)