From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.cs.columbia.edu, Oliver Upton <oupton@google.com>
Cc: will@kernel.org, tabba@google.com, qperret@google.com,
james.morse@arm.com, alexandru.elisei@arm.com,
kvm@vger.kernel.org, suzuki.poulose@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: arm64: Minor pKVM cleanups
Date: Tue, 10 May 2022 11:04:59 +0100 [thread overview]
Message-ID: <165217709150.1535314.2127016424159834600.b4-ty@kernel.org> (raw)
In-Reply-To: <20220509162559.2387784-1-oupton@google.com>
On Mon, 9 May 2022 16:25:57 +0000, Oliver Upton wrote:
> I was reading through some of the pKVM stuff to get an idea of how it
> handles feature registers and spotted a few minor nits.
>
> Applies cleanly to 5.18-rc5.
>
> Oliver Upton (2):
> KVM: arm64: pkvm: Drop unnecessary FP/SIMD trap handler
> KVM: arm64: pkvm: Don't mask already zeroed FEAT_SVE
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: pkvm: Drop unnecessary FP/SIMD trap handler
commit: 4d2e469e163ec79340b2f42c2a07838b5ff30686
[2/2] KVM: arm64: pkvm: Don't mask already zeroed FEAT_SVE
commit: 249838b7660ac04a67bfb017364a7f01029370a0
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-05-10 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:25 Oliver Upton
2022-05-09 16:25 ` [PATCH 1/2] KVM: arm64: pkvm: Drop unnecessary FP/SIMD trap handler Oliver Upton
2022-05-10 9:44 ` Fuad Tabba
2022-05-09 16:25 ` [PATCH 2/2] KVM: arm64: pkvm: Don't mask already zeroed FEAT_SVE Oliver Upton
2022-05-10 9:45 ` Fuad Tabba
2022-05-10 10:04 ` Marc Zyngier [this message]
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=165217709150.1535314.2127016424159834600.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@google.com \
--cc=qperret@google.com \
--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
all inboxes | Powered by JetHome®