public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Paul Mackerras" <paulus@ozlabs.org>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	kvm@vger.kernel.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag
Date: Wed, 15 May 2019 23:40:51 +0200	[thread overview]
Message-ID: <bcb4ef86-1bca-4f6a-2e31-eede09192672@redhat.com> (raw)
In-Reply-To: <20190514101327.GA13522@blackberry>

On 14/05/19 12:13, Paul Mackerras wrote:
> Paolo, Radim,
> 
> I have added 3 more commits to my kvm-ppc-next tree, for various fixes
> that have come in recently.  There is one bug fix, one spelling fix,
> and one commit that removes some code that does nothing.  The net
> result is 12 fewer lines of code in the kernel. :)
> 
> If you pull this tag and not the earlier kvm-ppc-next-5.2-1 tag, you
> might want to include the text from that tag in the commit message.
> That text is:
> 
> "
> PPC KVM update for 5.2
> 
> * Support for guests to access the new POWER9 XIVE interrupt controller
>   hardware directly, reducing interrupt latency and overhead for guests.
> 
> * In-kernel implementation of the H_PAGE_INIT hypercall.
> 
> * Reduce memory usage of sparsely-populated IOMMU tables.
> 
> * Several bug fixes.

Pulled, thanks.  Sorry for not following up on this before, my
travelling schedule was horrible for this merge window.

Paolo

      reply	other threads:[~2019-05-15 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 10:13 [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag Paul Mackerras
2019-05-15 21:40 ` 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=bcb4ef86-1bca-4f6a-2e31-eede09192672@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@ozlabs.org \
    --cc=rkrcmar@redhat.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