From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: Fixing KVM/ARM breakage in mainline
Date: Mon, 25 Feb 2013 12:18:27 +0000 [thread overview]
Message-ID: <512B5693.4000608@arm.com> (raw)
Russell, Marcelo, Gleb,
Commit 89f8833 (Merge tag 'kvm-3.9-1' of
git://git.kernel.org/pub/scm/virt/kvm/kvm) broke KVM/ARM. Nothing
fundamental, just annoying enough.
I've posted patches against next-20130215 some time ago:
http://comments.gmane.org/gmane.comp.emulators.kvm.devel/105019
I've now created a branch based off mainline as of this morning, and
containing these fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
kvm-arm/core-3.9-rc1-fixes
Now the question is: who wants to merge this? The diffstat looks like this:
Marc Zyngier (3):
ARM: KVM: fix kvm_arch_{prepare,commit}_memory_region
ARM: KVM: Rename KVM_MEMORY_SLOTS -> KVM_USER_MEM_SLOTS
ARM: KVM: fix compilation after removal of user_alloc from struct
kvm_memory_slot
arch/arm/include/asm/kvm_host.h | 2 +-
arch/arm/kvm/arm.c | 4 ++--
arch/arm/kvm/mmu.c | 5 -----
3 files changed, 3 insertions(+), 8 deletions(-)
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Russell King <linux@arm.linux.org.uk>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Christoffer Dall <cdall@cs.columbia.edu>
Subject: Fixing KVM/ARM breakage in mainline
Date: Mon, 25 Feb 2013 12:18:27 +0000 [thread overview]
Message-ID: <512B5693.4000608@arm.com> (raw)
Russell, Marcelo, Gleb,
Commit 89f8833 (Merge tag 'kvm-3.9-1' of
git://git.kernel.org/pub/scm/virt/kvm/kvm) broke KVM/ARM. Nothing
fundamental, just annoying enough.
I've posted patches against next-20130215 some time ago:
http://comments.gmane.org/gmane.comp.emulators.kvm.devel/105019
I've now created a branch based off mainline as of this morning, and
containing these fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
kvm-arm/core-3.9-rc1-fixes
Now the question is: who wants to merge this? The diffstat looks like this:
Marc Zyngier (3):
ARM: KVM: fix kvm_arch_{prepare,commit}_memory_region
ARM: KVM: Rename KVM_MEMORY_SLOTS -> KVM_USER_MEM_SLOTS
ARM: KVM: fix compilation after removal of user_alloc from struct
kvm_memory_slot
arch/arm/include/asm/kvm_host.h | 2 +-
arch/arm/kvm/arm.c | 4 ++--
arch/arm/kvm/mmu.c | 5 -----
3 files changed, 3 insertions(+), 8 deletions(-)
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next reply other threads:[~2013-02-25 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 12:18 Marc Zyngier [this message]
2013-02-25 12:18 ` Fixing KVM/ARM breakage in mainline Marc Zyngier
2013-02-25 12:21 ` Gleb Natapov
2013-02-25 12:21 ` Gleb Natapov
2013-03-03 11:47 ` Russell King - ARM Linux
2013-03-03 11:47 ` Russell King - ARM Linux
2013-03-03 11:53 ` Gleb Natapov
2013-03-03 11:53 ` Gleb Natapov
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=512B5693.4000608@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.