From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
amitk@kernel.org, rui.zhang@intel.com
Subject: Re: [PATCH v2 2/2] thermal: power_allocator: update once cooling devices when temp is low
Date: Wed, 21 Apr 2021 09:46:09 +0100 [thread overview]
Message-ID: <aa57e829-082a-6387-445b-d1f7aba488d9@arm.com> (raw)
In-Reply-To: <6ca7915a-9d31-10bd-4f9b-2f815a41df05@linaro.org>
On 4/20/21 10:03 PM, Daniel Lezcano wrote:
> On 20/04/2021 22:01, Lukasz Luba wrote:
>>
>>
>> On 4/20/21 4:24 PM, Daniel Lezcano wrote:
>>> On 20/04/2021 16:21, Lukasz Luba wrote:
>>>> Hi Daniel,
>>>>
>>>> On 4/20/21 2:30 PM, Daniel Lezcano wrote:
>>>>> On 19/04/2021 10:45, Lukasz Luba wrote:
>>>>
>>>> [snip]
>
> [ ... ]
>
>>
>> That new approach should work. I can test your patch with this new
>> functions and re-base my work on top of it.
>> Or you like me to write such patch and send it?
>
> At your convenience. I'm pretty busy ATM with more patches to review, so
> if you can handle that change that will be nice. Otherwise, I can take
> care of it but later.
>
OK, so I will create such patch and add your name in tags:
Co-developed-by: and Signed-off-by:
plus also a lore.kernel.org link in the patch commit message into this
discussion. Thanks for having a look at this.
Regards,
Lukasz
prev parent reply other threads:[~2021-04-21 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 8:45 [PATCH v2 0/2] Improve IPA mechanisms in low temperature state Lukasz Luba
2021-04-19 8:45 ` [PATCH v2 1/2] thermal: power_allocator: maintain the device statistics from going stale Lukasz Luba
2021-04-19 8:45 ` [PATCH v2 2/2] thermal: power_allocator: update once cooling devices when temp is low Lukasz Luba
2021-04-20 13:30 ` Daniel Lezcano
2021-04-20 14:21 ` Lukasz Luba
2021-04-20 15:24 ` Daniel Lezcano
2021-04-20 20:01 ` Lukasz Luba
2021-04-20 21:03 ` Daniel Lezcano
2021-04-21 8:46 ` 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=aa57e829-082a-6387-445b-d1f7aba488d9@arm.com \
--to=lukasz.luba@arm.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®