public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>, kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-next-5.6-2 tag
Date: Thu, 30 Jan 2020 11:54:16 +1100	[thread overview]
Message-ID: <20200130005416.GA25802@blackberry> (raw)

Paolo,

I have a second KVM PPC update for you.  I have added two more commits
which are both one-line fixes.  One is a compile warning fix and the
other fixes a locking error where we could incorrectly leave a mutex
locked when an error occurs.

Thanks,
Paul.

The following changes since commit 3a43970d55e9fd5475d3c4e5fe398ab831ec6c3a:

  KVM: PPC: Book3S HV: Implement H_SVM_INIT_ABORT hcall (2020-01-17 15:08:31 +1100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.6-2

for you to fetch changes up to fd24a8624eb29d3b6b7df68096ce0321b19b03c6:

  KVM: PPC: Book3S PR: Fix -Werror=return-type build failure (2020-01-29 16:47:45 +1100)

----------------------------------------------------------------
Second KVM PPC update for 5.6

* Fix compile warning on 32-bit machines
* Fix locking error in secure VM support

----------------------------------------------------------------
Bharata B Rao (1):
      KVM: PPC: Book3S HV: Release lock on page-out failure path

David Michael (1):
      KVM: PPC: Book3S PR: Fix -Werror=return-type build failure

 arch/powerpc/kvm/book3s_hv_uvmem.c | 2 +-
 arch/powerpc/kvm/book3s_pr.c       | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

                 reply	other threads:[~2020-01-30  0:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200130005416.GA25802@blackberry \
    --to=paulus@ozlabs.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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