From: Pierre Gondois <pierre.gondois@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ionela.Voinescu@arm.com, qperret@google.com,
Lukasz Luba <lukasz.luba@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH v3] sched/topology: Remove EM_MAX_COMPLEXITY limit
Date: Wed, 1 Feb 2023 17:16:41 +0100 [thread overview]
Message-ID: <66cfa719-6055-a521-6146-f629b7d0e446@arm.com> (raw)
In-Reply-To: <81d99fba-ce38-a9a4-4b80-aa3e2cc6f3c6@arm.com>
Hello Peter,
Please let me know if there are additional modifications required,
Regards,
Pierre
On 11/30/22 18:11, Dietmar Eggemann wrote:
> On 21/11/2022 10:43, Pierre Gondois wrote:
>> From: Pierre Gondois <Pierre.Gondois@arm.com>
>
> [...]
>
>> Signed-off-by: Pierre Gondois <Pierre.Gondois@arm.com>
>> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>>
>> Notes:
>> v2:
>> - Fix complexity computation in the commit message. [Dietmar]
>> - Use correct/latest function names. [Ionela]
>> - Added Rb from Lukasz.
>> v3:
>> - Keep paragraph 6.3 in sched-energy.rst with just a reference to
>> EM_MAX_NUM_CPUS, reference EM_MAX_NUM_CPUS in the commit message.
>> [Dietmar]
>
> Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
next prev parent reply other threads:[~2023-02-01 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 9:43 [PATCH v3] sched/topology: Remove EM_MAX_COMPLEXITY limit Pierre Gondois
2022-11-30 17:11 ` Dietmar Eggemann
2023-02-01 16:16 ` Pierre Gondois [this message]
2023-03-06 9:43 ` Pierre Gondois
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=66cfa719-6055-a521-6146-f629b7d0e446@arm.com \
--to=pierre.gondois@arm.com \
--cc=Ionela.Voinescu@arm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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;
as well as URLs for NNTP newsgroup(s).