From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: stable@vger.kernel.org, Doug Berger <opendmb@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Doug Berger <doug.berger@broadcom.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@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>,
"open list:SCHEDULER" <linux-kernel@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH stable 6.12] sched/deadline: only set free_cpus for online runqueues
Date: Fri, 31 Oct 2025 13:27:03 +0100 [thread overview]
Message-ID: <2025103157-effective-bulk-f9f6@gregkh> (raw)
In-Reply-To: <20251027224351.2893946-5-florian.fainelli@broadcom.com>
On Mon, Oct 27, 2025 at 03:43:49PM -0700, Florian Fainelli wrote:
> From: Doug Berger <opendmb@gmail.com>
>
> [ Upstream commit 382748c05e58a9f1935f5a653c352422375566ea ]
Not a valid git id :(
next prev parent reply other threads:[~2025-10-31 12:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 22:43 [PATCH stable 5.10] sched/deadline: only set free_cpus for online runqueues Florian Fainelli
2025-10-27 22:43 ` [PATCH stable 5.15] " Florian Fainelli
2025-10-27 22:43 ` [PATCH stable 5.4] " Florian Fainelli
2025-10-27 22:43 ` [PATCH stable 6.1] " Florian Fainelli
2025-10-27 22:43 ` [PATCH stable 6.12] " Florian Fainelli
2025-10-31 12:27 ` Greg Kroah-Hartman [this message]
2025-10-31 18:10 ` Florian Fainelli
2025-12-02 18:32 ` Florian Fainelli
2025-12-03 6:38 ` Greg Kroah-Hartman
2025-10-27 22:43 ` [PATCH stable 6.17] " Florian Fainelli
2025-10-27 22:43 ` [PATCH stable 6.6] " Florian Fainelli
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=2025103157-effective-bulk-f9f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=doug.berger@broadcom.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=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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