From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Paolo Bonzini <pbonzini@redhat.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 6.7, part #2
Date: Fri, 22 Dec 2023 13:16:41 +0000 [thread overview]
Message-ID: <69259c81441a57ceebcffb0e16895db1@kernel.org> (raw)
In-Reply-To: <784ab26d-8919-4f08-8440-f66432458492@sirena.org.uk>
On 2023-12-22 13:09, Mark Brown wrote:
> On Mon, Dec 18, 2023 at 11:17:24AM -0800, Oliver Upton wrote:
>
>> Here's the second batch of fixes for 6.7. Please note that this pull
>> is based on -rc4 instead of my first fixes tag as the KVM selftests
>> breakage was introduced by one of my changes that went through the
>> perf tree.
>
> Any news on this? The KVM selftests are still broken in mainline,
> pending-fixes and -next and the release is getting near.
>
> Oliver, should your tree be in -next?
No, we don't have the KVM/arm64 fixes in -next.
And we have another two weeks to release, so ample amount of
time until Paolo picks up the PR.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2023-12-22 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 19:17 [GIT PULL] KVM/arm64 fixes for 6.7, part #2 Oliver Upton
2023-12-22 13:09 ` Mark Brown
2023-12-22 13:16 ` Marc Zyngier [this message]
2023-12-22 13:26 ` Mark Brown
2023-12-22 13:34 ` Marc Zyngier
2023-12-22 14:20 ` Mark Brown
2023-12-22 23:25 ` Paolo Bonzini
2023-12-22 23:04 ` Paolo Bonzini
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=69259c81441a57ceebcffb0e16895db1@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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