From: Ingo Molnar <mingo@kernel.org>
To: Qais Yousef <qyousef@layalina.io>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Christian Loehle <christian.loehle@arm.com>,
Hongyan Xia <hongyan.xia2@arm.com>,
John Stultz <jstultz@google.com>,
Anjali K <anjalik@linux.ibm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] sched: Consolidate cpufreq updates
Date: Fri, 21 Feb 2025 16:47:55 +0100 [thread overview]
Message-ID: <Z7igK4w4PW1T_PCw@gmail.com> (raw)
In-Reply-To: <20250209235204.110989-1-qyousef@layalina.io>
* Qais Yousef <qyousef@layalina.io> wrote:
> ---
> include/linux/sched/cpufreq.h | 4 +-
> kernel/sched/core.c | 116 +++++++++++++++++++++++++++--
> kernel/sched/cpufreq_schedutil.c | 122 +++++++++++++++++++------------
> kernel/sched/deadline.c | 10 ++-
> kernel/sched/fair.c | 84 +++++++++------------
> kernel/sched/rt.c | 8 +-
> kernel/sched/sched.h | 9 ++-
> kernel/sched/syscalls.c | 30 ++++++--
> 8 files changed, 266 insertions(+), 117 deletions(-)
The changelog is rather long, and the diffstat is non-trivial.
Could you please split this up into multiple patches?
Thanks,
Ingo
next prev parent reply other threads:[~2025-02-21 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 23:52 [PATCH v8] sched: Consolidate cpufreq updates Qais Yousef
2025-02-21 15:47 ` Ingo Molnar [this message]
2025-02-23 0:03 ` Qais Yousef
2025-02-23 9:14 ` Ingo Molnar
2025-02-23 23:17 ` Qais Yousef
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=Z7igK4w4PW1T_PCw@gmail.com \
--to=mingo@kernel.org \
--cc=anjalik@linux.ibm.com \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=hongyan.xia2@arm.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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