From: Lukasz Luba <lukasz.luba@arm.com>
To: Javi Merino <javi.merino@kernel.org>
Cc: linux-pm@vger.kernel.org, edubezval@gmail.com,
rui.zhang@intel.com, orjan.eide@arm.com, chris.diamand@arm.com
Subject: Re: [PATCH v2 0/3] devfreq_cooling: let the driver supply the real power every time we need it
Date: Tue, 28 Feb 2017 13:52:53 +0000 [thread overview]
Message-ID: <1583912b-3581-a1d2-4b60-1072219d3f76@arm.com> (raw)
In-Reply-To: <20170221133559.GC23954@ct-lt-587>
Thank you Javi for the ACK.
On 21/02/17 13:35, Javi Merino wrote:
> On Tue, Jan 31, 2017 at 04:11:44PM +0000, Lukasz Luba wrote:
>> Hi,
>>
>> This patchset introduces a new interface for devfreq cooling in thermal
>> framework. The previous version of the patch can be seen here [1].
>> I have simplified the implementation and introduced resource utilization
>> scaling factor.
[..]
>>
>> The first patch contains some refactoring for getting the voltage,
>> the second implements the new feature, the third one changes trace function.
>> Patchset is based on v4.10-rc5.
I will have to rebase the patch set due to changes
introduced in merged tag pm-4.11-rc1 (OPP interface).
[..]
>>
>
> For the series:
>
> Acked-by: Javi Merino <javi.merino@kernel.org>
That would be a small v3 change, so should be simple.
Regards,
Lukasz
prev parent reply other threads:[~2017-02-28 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 16:11 [PATCH v2 0/3] devfreq_cooling: let the driver supply the real power every time we need it Lukasz Luba
2017-01-31 16:11 ` [PATCH v2 1/3] thermal: devfreq_cooling: refactor code and add get_voltage function Lukasz Luba
2017-01-31 16:11 ` [PATCH v2 2/3] thermal: devfreq_cooling: add new interface for direct power read Lukasz Luba
2017-02-21 13:34 ` Javi Merino
2017-01-31 16:11 ` [PATCH v2 3/3] trace: thermal: add another parameter *power to the tracing function Lukasz Luba
2017-02-21 13:35 ` [PATCH v2 0/3] devfreq_cooling: let the driver supply the real power every time we need it Javi Merino
2017-02-28 13:52 ` Lukasz Luba [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=1583912b-3581-a1d2-4b60-1072219d3f76@arm.com \
--to=lukasz.luba@arm.com \
--cc=chris.diamand@arm.com \
--cc=edubezval@gmail.com \
--cc=javi.merino@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=orjan.eide@arm.com \
--cc=rui.zhang@intel.com \
/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