From: Peter Zijlstra <peterz@infradead.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Doug Berger <opendmb@gmail.com>,
Juri Lelli <juri.lelli@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched/deadline: only set free_cpus for online runqueues
Date: Mon, 13 Oct 2025 21:17:41 +0200 [thread overview]
Message-ID: <20251013191741.GC2734756@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <1dc04a7b-d17b-4bca-9391-7d06d0c563fd@broadcom.com>
On Mon, Oct 13, 2025 at 11:22:36AM -0700, Florian Fainelli wrote:
> On 10/6/25 11:47, Peter Zijlstra wrote:
> > On Tue, Sep 23, 2025 at 11:03:18AM -0700, Doug Berger wrote:
> >
> > >
> > > Is there any way I can help to move this patch forward?
> >
> > Let me just apply it before it gets lost again. Sorry; sometimes the
> > amount of email is turning me into a goldfish with ADD :/
>
> Should we be able to see that patch in linux-next by now?
Should be in queue.git as of today, once the robot reports success I'll
push it towards tip.git, at which point it'll show up in -next.
next prev parent reply other threads:[~2025-10-13 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 1:22 [PATCH v2] sched/deadline: only set free_cpus for online runqueues Doug Berger
2025-08-18 12:58 ` Juri Lelli
2025-09-02 23:47 ` Florian Fainelli
2025-09-03 7:54 ` Peter Zijlstra
2025-09-05 4:43 ` Doug Berger
2025-09-23 18:03 ` Doug Berger
2025-10-02 19:15 ` Florian Fainelli
2025-10-06 18:47 ` Peter Zijlstra
2025-10-13 18:22 ` Florian Fainelli
2025-10-13 19:17 ` Peter Zijlstra [this message]
2025-10-16 9:33 ` [tip: sched/core] " tip-bot2 for Doug Berger
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=20251013191741.GC2734756@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=florian.fainelli@broadcom.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=opendmb@gmail.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