From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
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>,
K Prateek Nayak <kprateek.nayak@amd.com>
Subject: Re: Patch "sched/eevdf: Move to a single runqueue" has been added to the 7.2-stable tree
Date: Fri, 23 Oct 2026 15:01:25 +0200 [thread overview]
Message-ID: <2026102336-deodorant-repressed-45e8@gregkh> (raw)
In-Reply-To: <20261021131517.GN2823843@noisy.programming.kicks-ass.net>
On Wed, Oct 21, 2026 at 03:15:17PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 21, 2026 at 07:50:33AM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > sched/eevdf: Move to a single runqueue
> >
> > to the 7.2-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > sched-eevdf-move-to-a-single-runqueue.patch
> > and it can be found in the queue-7.2 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
>
> Ufff, why are we backporting this?
>
It was to fix:
Stable-dep-of: 2f93bcb3f9aa ("sched/fair: Avoid overflow in place_entity()")
but that's a mess, too many follow-on patches needed here. I've dropped
it and a few others.
If someone has a "simple" backport of the above commit, we'll take that
instead.
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-23 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261021115034.4170616-1-sashal@kernel.org>
2026-10-21 13:15 ` Patch "sched/eevdf: Move to a single runqueue" has been added to the 7.2-stable tree Peter Zijlstra
2026-10-23 13:01 ` Greg KH [this message]
2026-10-23 20:02 ` Sasha Levin
2026-10-26 9:51 ` Vincent Guittot
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=2026102336-deodorant-repressed-45e8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable-commits@vger.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