From: gleb@redhat.com (Gleb Natapov)
To: linux-arm-kernel@lists.infradead.org
Subject: Fixing KVM/ARM breakage in mainline
Date: Mon, 25 Feb 2013 14:21:17 +0200 [thread overview]
Message-ID: <20130225122117.GE12299@redhat.com> (raw)
In-Reply-To: <512B5693.4000608@arm.com>
On Mon, Feb 25, 2013 at 12:18:27PM +0000, Marc Zyngier wrote:
> 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:
>
I was going to merge it today.
--
Gleb.
next prev parent reply other threads:[~2013-02-25 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 12:18 Fixing KVM/ARM breakage in mainline Marc Zyngier
2013-02-25 12:21 ` Gleb Natapov [this message]
2013-03-03 11:47 ` Russell King - ARM Linux
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=20130225122117.GE12299@redhat.com \
--to=gleb@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).