From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Leon Romanovsky <leon@kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
Steve Wahl <steve.wahl@hpe.com>,
x86@kernel.org
Subject: Re: [tip: sched/urgent] sched/fair: Use sched_domain_span() for topology_span_sane()
Date: Fri, 4 Jul 2025 12:32:44 +0200 [thread overview]
Message-ID: <20250704103244.GA2307777@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250704102103.GAaGerDxWX7VhePA3j@fat_crate.local>
On Fri, Jul 04, 2025 at 12:21:03PM +0200, Borislav Petkov wrote:
> On Fri, Jul 04, 2025 at 09:13:16AM -0000, tip-bot2 for K Prateek Nayak wrote:
> > The following commit has been merged into the sched/urgent branch of tip:
> >
> > Commit-ID: 02bb4259ca525efa39a2531cb630329fb87fc968
> > Gitweb: https://git.kernel.org/tip/02bb4259ca525efa39a2531cb630329fb87fc968
> > Author: K Prateek Nayak <kprateek.nayak@amd.com>
> > AuthorDate: Mon, 30 Jun 2025 06:10:59
> > Committer: Peter Zijlstra <peterz@infradead.org>
> > CommitterDate: Fri, 04 Jul 2025 10:35:56 +02:00
> >
> > sched/fair: Use sched_domain_span() for topology_span_sane()
>
> My guest doesn't like this one and reverting it ontop of the whole tip lineup
> fixes it.
OK, let me pull this patch real quick for now. Clearly it needs moar
work.
next prev parent reply other threads:[~2025-07-04 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 6:10 [PATCH v2] " K Prateek Nayak
2025-06-30 14:39 ` Steve Wahl
2025-07-03 16:00 ` Valentin Schneider
2025-07-04 9:13 ` [tip: sched/urgent] " tip-bot2 for K Prateek Nayak
2025-07-04 10:21 ` Borislav Petkov
2025-07-04 10:32 ` Peter Zijlstra [this message]
2025-07-04 11:46 ` K Prateek Nayak
2025-07-04 12:33 ` Borislav Petkov
2025-07-07 3:26 ` K Prateek Nayak
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=20250704103244.GA2307777@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=kprateek.nayak@amd.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=steve.wahl@hpe.com \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®