[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <573084CA.6020708@linux.vnet.ibm.com>
Date: Mon, 9 May 2016 18:08:34 +0530
From: Akshay Adiga <akshay.adiga@...ux.vnet.ibm.com>
To: rjw@...ysocki.net, viresh.kumar@...aro.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH-next v2 0/2] cpufreq: powernv: Fixes for Global pstate
management
On 05/03/2016 08:49 PM, Akshay Adiga wrote:
> Fixes are based on patch https://patchwork.ozlabs.org/patch/612058/ which
> is in Rafael's linux-next.
>
> - Patch [1] fixes WARN_ON in powernv_target_index()
> - Patch [2] Deleting any pending timer to saves an unnecessary irq call
> in powernv_target_index()
>
> Akshay Adiga (2):
> cpufreq: powernv: Move smp_call_function_any() out of irq safe block
> cpufreq: powernv: del_timer_sync when global and local pstate are
> equal
>
> drivers/cpufreq/powernv-cpufreq.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
Does this look good ? Anything i should do ?
Regards
Akshay Adiga
Powered by blists - more mailing lists