From: Paolo Bonzini <pbonzini@redhat.com>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Jing Zhang <jingzhangos@google.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Vincent Donnefort <vdonnefort@google.com>,
Kristina Martsenko <kristina.martsenko@arm.com>,
Miguel Luis <miguel.luis@oracle.com>
Subject: Re: [GIT PULL] KVM/arm64 updates for 6.7
Date: Tue, 31 Oct 2023 22:18:16 +0100 [thread overview]
Message-ID: <03ff2765-2785-4590-8b92-19fdcf67d71e@redhat.com> (raw)
In-Reply-To: <ZUFL9AUV36xHGaBE@thinky-boi>
On 10/31/23 19:48, Oliver Upton wrote:
> Hi Paolo, Here's the pile of KVM/arm64 changes for 6.7. Almost all of
> these changes have been baking in -next for a while, although I did need
> to rebase to back out a broken change last minute. I'm only aware of a
> single (trivial) conflict with the arm64 tree resulting from a moved
> cpucap check, resolution below. Please pull.
Pulled, thanks.
Paolo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-10-31 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 18:48 [GIT PULL] KVM/arm64 updates for 6.7 Oliver Upton
2023-10-31 21:18 ` Paolo Bonzini [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=03ff2765-2785-4590-8b92-19fdcf67d71e@redhat.com \
--to=pbonzini@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kristina.martsenko@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=miguel.luis@oracle.com \
--cc=oliver.upton@linux.dev \
--cc=rananta@google.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--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