From: Roman Kisel <romank@linux.microsoft.com>
To: Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>
Cc: Jack Thomson <jackabt.amazon@gmail.com>,
mark.rutland@arm.com, lpieralisi@kernel.org,
sudeep.holla@arm.com, arnd@arndb.de, wei.liu@kernel.org,
mhklinux@outlook.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, oliver.upton@linux.dev,
kvmarm@lists.linux.dev, roypat@amazon.com,
Jack Thomson <jackabt@amazon.com>
Subject: Re: [PATCH] arm64: kvm, smccc: Fix vendor uuid
Date: Mon, 21 Jul 2025 10:27:07 -0700 [thread overview]
Message-ID: <9f39e539-3216-4f5d-819f-9500f76a0154@linux.microsoft.com> (raw)
In-Reply-To: <aH51jfOmPfF3XEke@willie-the-truck>
On 7/21/2025 10:14 AM, Will Deacon wrote:
> On Mon, Jul 21, 2025 at 04:59:36PM +0100, Marc Zyngier wrote:
[...]
>>
>> Irk. This is remarkably embarrassing, and needs to be addressed ASAP,
>> before 6.16 ships. FWIW, I've just posted a quickly whipped selftest
>> that shows the problem[1].
>>
>> Will, is there a chance you can pick this up and ferry it to Linus?
>> If you do, please add:
>>
>> Reviewed-by: Marc Zyngier <maz@kernel.org>
>> Tested-by: Marc Zyngier <maz@kernel.org>
>
> Sure, I'll grab it. Thanks!
>
I'm sorry for that, apologies for screwing things up :(
Very much appreciate the fix and the test. I clearly missed testing
backward compat. with the old kernels.
> Will
--
Thank you,
Roman
next prev parent reply other threads:[~2025-07-21 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 13:05 [PATCH] arm64: kvm, smccc: Fix vendor uuid Jack Thomson
2025-07-21 15:59 ` Marc Zyngier
2025-07-21 17:14 ` Will Deacon
2025-07-21 17:27 ` Roman Kisel [this message]
2025-07-21 16:15 ` Sudeep Holla
2025-07-21 17:20 ` Roman Kisel
2025-07-21 17:45 ` Will Deacon
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=9f39e539-3216-4f5d-819f-9500f76a0154@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=arnd@arndb.de \
--cc=jackabt.amazon@gmail.com \
--cc=jackabt@amazon.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mhklinux@outlook.com \
--cc=oliver.upton@linux.dev \
--cc=roypat@amazon.com \
--cc=sudeep.holla@arm.com \
--cc=wei.liu@kernel.org \
--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