From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Meelis Roos <mroos@linux.ee>, rjw@rjwysocki.net, viresh.kumar@linaro.org
Cc: ego@linux.vnet.ibm.com, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end
Date: Wed, 21 May 2014 18:02:51 +0530 [thread overview]
Message-ID: <537C9CF3.60503@linux.vnet.ibm.com> (raw)
In-Reply-To: <5367553C.1040701@linux.vnet.ibm.com>
On 05/05/2014 02:39 PM, Srivatsa S. Bhat wrote:
> On 05/05/2014 02:23 PM, Meelis Roos wrote:
>>>
>>> Changes in v3:
>>> Expanded the comment in the code to briefly mention why ASYNC_NOTIFICATION
>>> drivers are left out from the check, as suggested by Gautham R. Shenoy.
>>> No code changes in this version.
>>>
>>> v2: https://lkml.org/lkml/2014/4/29/283
>>> v1: https://lkml.org/lkml/2014/4/28/469
>>
>> Seems to work on VIA EPIA with 3.15-rc2 (no other cpufreq fixes):
>>
>
> Great! Thanks a lot for testing this!
>
> Rafael/Viresh, can you please add Meelis' Tested-by while taking
> this patch?
Rafael, any thoughts on this patch?
It has been Acked by Viresh and tested by Meelis. Hope you'll consider
picking up this patch for 3.16.
Thank you!
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2014-05-21 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 7:22 [PATCH v3] cpufreq: Catch double invocations of cpufreq_freq_transition_begin/end Srivatsa S. Bhat
2014-05-05 8:53 ` Meelis Roos
2014-05-05 9:09 ` Srivatsa S. Bhat
2014-05-21 12:32 ` Srivatsa S. Bhat [this message]
2014-05-21 13:01 ` Rafael J. Wysocki
2014-05-21 12:48 ` Srivatsa S. Bhat
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=537C9CF3.60503@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=cpufreq@vger.kernel.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).