mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, Dietmar.Eggemann@arm.com,
	ionela.voinescu@arm.com
Subject: Re: [PATCH v4 0/3] Improve the estimations in Intelligent Power Allocation
Date: Thu, 26 Nov 2020 14:45:13 +0000	[thread overview]
Message-ID: <9680cd44-c22e-2f5e-43ec-4a7f16680a45@arm.com> (raw)
In-Reply-To: <fc3228c2-d668-6f32-8965-00896b630351@linaro.org>



On 11/26/20 2:30 PM, Daniel Lezcano wrote:
> On 26/11/2020 15:02, Lukasz Luba wrote:
> 
> [ ... ]
> 
>>>> changed via sysfs.
>>>>
>>>> Could you take it please? It should apply smoothly in your tree.
>>>
>>> Actually, I'm waiting for Ionela and Dietmar ack.
>>>
>>>
>>
>> Are they maintainers of this file that you need their ACKs?
>> Maybe I should drop mine then.
> 
> Ok let me clarify :)
> 
> In general when someone comments on the changes, I usually wait for the
> consensus before merging the patches. If the persons who commented
> before are unresponsive, depending on the context and my perception, I
> apply the changes or not.
> 
> I'm giving the opportunity to Ionela to review the series again as she
> commented the previous version (and gave a reviewed-by). I thought also
> Dietmar commented the series but apparently I was wrong.
> 
> As you stated, you are the maintainer of the subsystem, so if there are
> no acked-by or reviewed-by, the series will be applied anyway soon.
> 
> Meanwhile, they are in the 'testing' branch of the tree, the antechamber
> of 'linux-next' and 'next' ;)
> 

Thank you clarifying this and taking the patches into the testing
branch.

Regards,
Lukasz

      reply	other threads:[~2020-11-26 14:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 16:10 Lukasz Luba
2020-11-24 16:10 ` [PATCH v4 1/3] thermal: power allocator: change the 'k_i' coefficient estimation Lukasz Luba
2020-11-26 16:00   ` Ionela Voinescu
2020-11-24 16:10 ` [PATCH v4 2/3] thermal: power allocator: refactor sustainable power estimation Lukasz Luba
2020-11-26 15:59   ` Ionela Voinescu
2020-11-26 16:26     ` Lukasz Luba
2020-11-24 16:10 ` [PATCH v4 3/3] thermal: power allocator: change the 'k_*' always in estimate_pid_constants() Lukasz Luba
2020-11-26 16:00   ` Ionela Voinescu
2020-11-26 12:49 ` [PATCH v4 0/3] Improve the estimations in Intelligent Power Allocation Lukasz Luba
2020-11-26 13:09   ` Daniel Lezcano
2020-11-26 14:02     ` Lukasz Luba
2020-11-26 14:30       ` Daniel Lezcano
2020-11-26 14:45         ` 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=9680cd44-c22e-2f5e-43ec-4a7f16680a45@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=Dietmar.Eggemann@arm.com \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=ionela.voinescu@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome