From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, arvind.chauhan@arm.com
Subject: Re: [PATCH 0/2] CPUFreq core fixes for v3.10-rc2
Date: Thu, 02 May 2013 23:19:10 +0200 [thread overview]
Message-ID: <1496263.0WG0vFmtlD@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1367332148.git.viresh.kumar@linaro.org>
On Tuesday, April 30, 2013 08:02:16 PM Viresh Kumar wrote:
> I just saw your pull request and so these should go in rc2 now.
>
> These are fixes for cpufreq core and common governor part. They mostly impact
> systems which have set have_governor_per_policy to true. i.e. big LITTLE cpufreq
> driver.
>
> Viresh Kumar (2):
> cpufreq: governors: Fix CPUFREQ_GOV_POLICY_{INIT|EXIT} notifiers
> cpufreq: Issue CPUFREQ_GOV_POLICY_EXIT notifier before dropping
> policy refcount
>
> drivers/cpufreq/cpufreq.c | 6 +++---
> drivers/cpufreq/cpufreq_governor.c | 11 +++++++----
> drivers/cpufreq/cpufreq_governor.h | 1 +
> 3 files changed, 11 insertions(+), 7 deletions(-)
Both queued up for the v3.10-rc2 push.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-05-02 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 14:32 Viresh Kumar
2013-04-30 14:32 ` [PATCH 1/2] cpufreq: governors: Fix CPUFREQ_GOV_POLICY_{INIT|EXIT} notifiers Viresh Kumar
2013-04-30 14:32 ` [PATCH 2/2] cpufreq: Issue CPUFREQ_GOV_POLICY_EXIT notifier before dropping policy refcount Viresh Kumar
2013-05-02 21:19 ` Rafael J. Wysocki [this message]
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=1496263.0WG0vFmtlD@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=robin.randhawa@arm.com \
--cc=viresh.kumar@linaro.org \
/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
all inboxes | Powered by JetHome®