On 29 April 2014 18:36, Srivatsa S. Bhat
wrote:
> Some cpufreq drivers were redundantly invoking the _begin() and _end()
> APIs around frequency transitions, and this double invocation (one from
> the cpufreq core and the other from the cpufreq driver) used to result
> in a self-deadlock, leading
On 04/29/2014 06:39 PM, Meelis Roos wrote:
>>
>> Signed-off-by: Srivatsa S. Bhat
>> ---
>>
>> v2: Removed the coverage of ASYNC_NOTIFICATION drivers, in order to avoid
>> false-positives.
>
> I am confused - on top of what patches should I test it?
>
>
Well, actually this is not a fix. Its
>
> Signed-off-by: Srivatsa S. Bhat
> ---
>
> v2: Removed the coverage of ASYNC_NOTIFICATION drivers, in order to avoid
> false-positives.
I am confused - on top of what patches should I test it?
>
> drivers/cpufreq/cpufreq.c |7 +++
> include/linux/cpufreq.h |1 +
> 2 files
Some cpufreq drivers were redundantly invoking the _begin() and _end()
APIs around frequency transitions, and this double invocation (one from
the cpufreq core and the other from the cpufreq driver) used to result
in a self-deadlock, leading to system hangs during boot. (The _begin()
API makes
Some cpufreq drivers were redundantly invoking the _begin() and _end()
APIs around frequency transitions, and this double invocation (one from
the cpufreq core and the other from the cpufreq driver) used to result
in a self-deadlock, leading to system hangs during boot. (The _begin()
API makes
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
v2: Removed the coverage of ASYNC_NOTIFICATION drivers, in order to avoid
false-positives.
I am confused - on top of what patches should I test it?
drivers/cpufreq/cpufreq.c |7 +++
On 04/29/2014 06:39 PM, Meelis Roos wrote:
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
v2: Removed the coverage of ASYNC_NOTIFICATION drivers, in order to avoid
false-positives.
I am confused - on top of what patches should I test it?
Well, actually this is
On 29 April 2014 18:36, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
Some cpufreq drivers were redundantly invoking the _begin() and _end()
APIs around frequency transitions, and this double invocation (one from
the cpufreq core and the other from the cpufreq driver) used to result
8 matches
Mail list logo