From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>, kvm@vger.kernel.org
Cc: Alexander Graf <agraf@suse.de>, kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next branch
Date: Fri, 15 Jan 2016 17:49:59 +0100 [thread overview]
Message-ID: <56992337.9020702@redhat.com> (raw)
In-Reply-To: <20160115103515.GA8750@fergus.ozlabs.ibm.com>
On 15/01/2016 11:35, Paul Mackerras wrote:
> Hi Paolo,
>
> Please do a pull from my kvm-ppc-next branch to get a PPC update for
> v4.5. All of these commits have been in linux-next for weeks except
> for the get/set_one_reg fix for Altivec from Greg Kurz, which was in
> linux-next today and is a really simple and obvious fix.
>
> Thanks,
> Paul.
>
> The following changes since commit 460146348518a1c4e810d01baf81847f8c6a1c73:
>
> Merge tag 'kvm-s390-next-4.5-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2015-12-02 13:50:04 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git kvm-ppc-next
>
> for you to fetch changes up to b4d7f161feb3015d6306e1d35b565c888ff70c9d:
>
> KVM: PPC: Fix ONE_REG AltiVec support (2016-01-14 14:43:35 +1100)
>
> ----------------------------------------------------------------
> Geyslan G. Bem (1):
> KVM: PPC: Book3S PR: Remove unused variable 'vcpu_book3s'
>
> Greg Kurz (1):
> KVM: PPC: Fix ONE_REG AltiVec support
>
> Paul Mackerras (1):
> KVM: PPC: Book3S HV: Handle unexpected traps in guest entry/exit code better
>
> Thomas Huth (2):
> KVM: PPC: Fix emulation of H_SET_DABR/X on POWER8
> KVM: PPC: Increase memslots to 512
>
> arch/powerpc/include/asm/kvm_host.h | 3 +--
> arch/powerpc/kvm/book3s_64_mmu.c | 3 ---
> arch/powerpc/kvm/book3s_hv.c | 18 ++++++++++++++++++
> arch/powerpc/kvm/book3s_hv_rmhandlers.S | 4 +++-
> arch/powerpc/kvm/powerpc.c | 20 ++++++++++----------
> 5 files changed, 32 insertions(+), 16 deletions(-)
>
Pulled, thanks.
Paolo
next prev parent reply other threads:[~2016-01-15 16:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 10:35 [GIT PULL] Please pull my kvm-ppc-next branch Paul Mackerras
2016-01-15 16:49 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-02 6:54 Paul Mackerras
2017-11-02 17:16 ` Paolo Bonzini
2017-09-01 6:36 Paul Mackerras
2017-07-02 7:11 Paul Mackerras
2017-04-21 7:52 Paul Mackerras
2017-04-21 10:28 ` Paolo Bonzini
2017-04-19 11:01 Paul Mackerras
2017-04-19 12:32 ` Alexey Kardashevskiy
2017-04-20 1:28 ` Paul Mackerras
2017-02-19 23:25 Paul Mackerras
2017-02-01 9:24 Paul Mackerras
2017-02-07 17:17 ` Paolo Bonzini
2016-12-06 9:35 Paul Mackerras
2016-12-06 13:50 ` Radim Krčmář
2016-11-28 22:53 Paul Mackerras
2016-11-30 17:25 ` Radim Krčmář
2016-09-28 4:46 Paul Mackerras
2016-09-29 14:46 ` Radim Krčmář
2016-09-29 20:00 ` Thomas Huth
2016-09-13 4:58 Paul Mackerras
2016-09-13 13:10 ` Paolo Bonzini
2016-07-11 15:46 Paul Mackerras
2016-07-11 16:11 ` Paolo Bonzini
2016-05-13 5:23 Paul Mackerras
2016-05-13 7:44 ` Christian Borntraeger
2016-05-13 8:24 ` Paul Mackerras
2016-03-03 2:38 Paul Mackerras
2016-03-03 13:46 ` Paolo Bonzini
2015-10-26 4:17 Paul Mackerras
2015-11-02 12:53 ` Paolo Bonzini
2015-09-05 7:45 Paul Mackerras
2015-09-07 8:29 ` 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=56992337.9020702@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@ozlabs.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).