From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: cw00.choi@samsung.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, vireshk@kernel.org, rafael@kernel.org,
Dietmar.Eggemann@arm.com, amitk@kernel.org, rui.zhang@intel.com,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com
Subject: Re: [RFC][PATCH 0/3] New thermal interface allowing IPA to get max power
Date: Mon, 1 Feb 2021 16:37:58 +0000 [thread overview]
Message-ID: <1d0bd56f-be68-2306-3ed6-511e1d533148@arm.com> (raw)
In-Reply-To: <de40eb55-8309-e9a5-68da-eab936cd0580@linaro.org>
Hi Daniel,
On 2/1/21 2:21 PM, Daniel Lezcano wrote:
>
> Hi Lukasz,
>
> On 01/02/2021 12:23, Lukasz Luba wrote:
>> Daniel, Chanwoo
>>
>> Gentle ping. Have you have a chance to check these patches?
>
> I will review the patches in a couple of days
Thank you, I will wait then.
Regards,
Lukasz
>
> -- Daniel
>
>
next prev parent reply other threads:[~2021-02-01 16:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 10:39 [RFC][PATCH 0/3] New thermal interface allowing IPA to get max power Lukasz Luba
2021-01-26 10:39 ` [RFC][PATCH 1/3] PM /devfreq: add user frequency limits into devfreq struct Lukasz Luba
2021-02-03 10:11 ` Chanwoo Choi
2021-02-03 10:21 ` Lukasz Luba
2021-02-11 11:07 ` Lukasz Luba
2021-02-11 22:27 ` Lukasz Luba
2021-02-15 15:00 ` Chanwoo Choi
2021-02-16 10:41 ` Lukasz Luba
2021-02-24 8:04 ` Chanwoo Choi
2021-01-26 10:40 ` [RFC][PATCH 2/3] thermal: devfreq_cooling: add new callback to get user limit for min state Lukasz Luba
2021-01-26 10:40 ` [RFC][PATCH 3/3] thermal: power_allocator: get proper max power limited by user Lukasz Luba
2021-01-27 9:15 ` [RFC][PATCH 0/3] New thermal interface allowing IPA to get max power Viresh Kumar
2021-01-27 10:11 ` Lukasz Luba
2021-01-27 10:13 ` Viresh Kumar
2021-02-01 11:23 ` Lukasz Luba
2021-02-01 14:21 ` Daniel Lezcano
2021-02-01 16:37 ` Lukasz Luba [this message]
2021-02-02 9:31 ` Chanwoo Choi
2021-02-02 9:56 ` Lukasz Luba
2021-02-01 14:19 ` Rafael J. Wysocki
2021-02-01 16:37 ` Lukasz Luba
2021-02-22 10:22 ` Daniel Lezcano
2021-02-22 12:10 ` Lukasz Luba
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=1d0bd56f-be68-2306-3ed6-511e1d533148@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=amitk@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vireshk@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.