[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokaHU0V86DPB7nEQ8ndwu_mJ_x_Uz47XPHZeyAW3hcP_w@mail.gmail.com>
Date: Wed, 11 Sep 2013 13:36:58 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Guennadi Liakhovetski <g.liakhovetski@....de>
Cc: Greg KH <greg@...ah.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
SH-Linux <linux-sh@...r.kernel.org>,
Magnus Damm <magnus.damm@...il.com>
Subject: Re: "cpufreq: fix serialization issues with freq change notifiers"
breaks cpufreq too
On 10 September 2013 22:37, Guennadi Liakhovetski <g.liakhovetski@....de> 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
Download attachment "0001-cpufreq-distinguish-drivers-that-do-asynchronous-not.patch" of type "application/octet-stream" (2313 bytes)
Download attachment "0002-cpufreq-fix-notification-serialization-issues.patch" of type "application/octet-stream" (4388 bytes)
Powered by blists - more mailing lists