From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>, Fuad Tabba <tabba@google.com>,
Oliver Upton <oupton@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: pKVM breakage in mainline on n1sdp
Date: Mon, 23 Feb 2026 10:05:46 +0000 [thread overview]
Message-ID: <aZwmevKcvW2HxdJ5@J2N7QTR9R3> (raw)
In-Reply-To: <aZm2XCZLYxgxL99d@sirena.co.uk>
On Sat, Feb 21, 2026 at 01:42:52PM +0000, Mark Brown wrote:
> On Sat, Feb 21, 2026 at 10:38:05AM +0000, Marc Zyngier wrote:
>
> > If that's vanilla 6.19, then there is post Feb 8th. Sorry for the
> > unwarranted rant.
>
> It won't be vanilla v6.19, that specific log will be tip of Linus' tree
> from yesterday morning UK time which should be 8bf22c33e7a1 ("Merge tag
> 'net-7.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net"),
> there were a few results for commits over the day prior to that showing
> the same behaviour.
Are you sure? That log says:
CPU: 1 UID: 0 PID: 1955 Comm: qemu-system-aar Not tainted 6.19.0 #1 PREEMPT
... where "6.19.0" means that's the 6.19 tag, and "#1" means that's the
first build against that.
Is the build system overriding things such that this is misleading?
Is there potentially a problem with the build system?
Mark.
next prev parent reply other threads:[~2026-02-23 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 19:08 pKVM breakage in mainline on n1sdp Mark Brown
2026-02-21 10:33 ` Marc Zyngier
2026-02-21 10:38 ` Marc Zyngier
2026-02-21 12:35 ` Marc Zyngier
2026-02-21 13:42 ` Mark Brown
2026-02-23 10:05 ` Mark Rutland [this message]
2026-02-23 14:27 ` Mark Brown
2026-02-21 13:16 ` Mark Brown
2026-02-22 8:34 ` Fuad Tabba
2026-02-23 16:26 ` Mark Brown
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=aZwmevKcvW2HxdJ5@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@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