From: Viresh Kumar <viresh.kumar@linaro.org>
To: Akshay Adiga <akshay.adiga@linux.vnet.ibm.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH-next v2 0/2] cpufreq: powernv: Fixes for Global pstate management
Date: Mon, 9 May 2016 21:02:04 +0530 [thread overview]
Message-ID: <20160509153204.GA21661@vireshk-i7> (raw)
In-Reply-To: <1462288776-26721-1-git-send-email-akshay.adiga@linux.vnet.ibm.com>
On 03-05-16, 20:49, 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
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2016-05-09 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 15:19 [PATCH-next v2 0/2] cpufreq: powernv: Fixes for Global pstate management Akshay Adiga
2016-05-03 15:19 ` [PATCH-next v2 1/2] cpufreq: powernv: Move smp_call_function_any() out of irq safe block Akshay Adiga
2016-05-03 15:19 ` [PATCH-next v2 2/2] cpufreq: powernv: del_timer_sync when global and local pstate are equal Akshay Adiga
2016-05-09 12:38 ` [PATCH-next v2 0/2] cpufreq: powernv: Fixes for Global pstate management Akshay Adiga
2016-05-09 15:32 ` Viresh Kumar [this message]
2016-05-13 22:08 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160509153204.GA21661@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).