From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/2] KVM/ARM Fixes for 3.19
Date: Mon, 12 Jan 2015 11:15:00 +0100 [thread overview]
Message-ID: <54B39EA4.50808@redhat.com> (raw)
In-Reply-To: <1420981811-18731-1-git-send-email-christoffer.dall@linaro.org>
On 11/01/2015 14:10, Christoffer Dall wrote:
> Hi Paolo,
>
> The following changes since commit b1940cd21c0f4abdce101253e860feff547291b0:
>
> Linux 3.19-rc3 (2015-01-05 17:05:20 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvm-arm-fixes-3.19
>
> for you to fetch changes up to b5b8ddba844c6b6c5b96c27b284d9ed05a16fa13:
>
> arm64: KVM: Fix HCR setting for 32bit guests (2015-01-11 13:54:51 +0100)
>
> (Note that I got an extra merge commit when merging kvm/master into
> kvmarm/master, which I think is because Linus applied the set of fixes
> from kvmarm/master directly from Marc's patches. Let me know if you need
> me to mangle this differently somehow.)
Hmm, that's a bit ugly. I'll apply the patches directly too, please do
a "git reset --hard kvm/master" before applying more stuff.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Cc: Marc Zyngier <marc.zyngier@arm.com>, kvm@vger.kernel.org
Subject: Re: [GIT PULL 0/2] KVM/ARM Fixes for 3.19
Date: Mon, 12 Jan 2015 11:15:00 +0100 [thread overview]
Message-ID: <54B39EA4.50808@redhat.com> (raw)
In-Reply-To: <1420981811-18731-1-git-send-email-christoffer.dall@linaro.org>
On 11/01/2015 14:10, Christoffer Dall wrote:
> Hi Paolo,
>
> The following changes since commit b1940cd21c0f4abdce101253e860feff547291b0:
>
> Linux 3.19-rc3 (2015-01-05 17:05:20 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvm-arm-fixes-3.19
>
> for you to fetch changes up to b5b8ddba844c6b6c5b96c27b284d9ed05a16fa13:
>
> arm64: KVM: Fix HCR setting for 32bit guests (2015-01-11 13:54:51 +0100)
>
> (Note that I got an extra merge commit when merging kvm/master into
> kvmarm/master, which I think is because Linus applied the set of fixes
> from kvmarm/master directly from Marc's patches. Let me know if you need
> me to mangle this differently somehow.)
Hmm, that's a bit ugly. I'll apply the patches directly too, please do
a "git reset --hard kvm/master" before applying more stuff.
Paolo
next prev parent reply other threads:[~2015-01-12 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 13:10 [GIT PULL 0/2] KVM/ARM Fixes for 3.19 Christoffer Dall
2015-01-11 13:10 ` Christoffer Dall
2015-01-11 13:10 ` [GIT PULL 1/2] arm64: KVM: Fix TLB invalidation by IPA/VMID Christoffer Dall
2015-01-11 13:10 ` Christoffer Dall
2015-01-11 13:10 ` [GIT PULL 2/2] arm64: KVM: Fix HCR setting for 32bit guests Christoffer Dall
2015-01-11 13:10 ` Christoffer Dall
2015-01-12 10:15 ` Paolo Bonzini [this message]
2015-01-12 10:15 ` [GIT PULL 0/2] KVM/ARM Fixes for 3.19 Paolo Bonzini
2015-01-12 17:19 ` Christoffer Dall
2015-01-12 17:19 ` Christoffer Dall
2015-01-12 18:36 ` Paolo Bonzini
2015-01-12 18:36 ` Paolo Bonzini
2015-01-12 18:47 ` Christoffer Dall
2015-01-12 18:47 ` Christoffer Dall
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=54B39EA4.50808@redhat.com \
--to=pbonzini@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 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.