All of lore.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(-)

WARNING: multiple messages have this Message-ID (diff)
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 00:54:16 +0000	[thread overview]
Message-ID: <20200130005416.GA25802@blackberry> (raw)
In-Reply-To: <20190222051405.GA2527@blackberry>

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: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30  0:54 Paul Mackerras [this message]
2020-01-30  0:54 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-2 tag Paul Mackerras
  -- strict thread matches above, loose matches on Subject: below --
2021-02-11  7:25 [GIT PULL] Please pull my kvm-ppc-next-5.12-1 tag Paul Mackerras
2021-02-11  7:25 ` Paul Mackerras
2021-02-11 13:00 ` Paolo Bonzini
2021-02-11 13:00   ` Paolo Bonzini
2020-09-22  4:19 [GIT PULL] Please pull my kvm-ppc-next-5.10-1 tag Paul Mackerras
2020-09-22  4:19 ` Paul Mackerras
2020-09-22 12:18 ` Paolo Bonzini
2020-09-22 12:18   ` Paolo Bonzini
2020-07-28  5:51 [GIT PULL] Please pull my kvm-ppc-next-5.9-1 tag Paul Mackerras
2020-07-28  5:51 ` Paul Mackerras
2020-08-05  0:02 ` Paul Mackerras
2020-08-05  0:02   ` Paul Mackerras
2020-08-07 12:23   ` Paolo Bonzini
2020-08-07 12:23     ` Paolo Bonzini
2020-06-01 23:53 [GIT PULL] Please pull my kvm-ppc-next-5.8-1 tag Paul Mackerras
2020-06-01 23:53 ` Paul Mackerras
2020-06-04 18:58 ` Paolo Bonzini
2020-06-04 18:58   ` Paolo Bonzini
2020-06-11  0:48   ` Paul Mackerras
2020-06-11  0:48     ` Paul Mackerras
2020-06-11  1:01     ` Paolo Bonzini
2020-06-11  1:01       ` Paolo Bonzini
2020-03-30 23:08 [GIT PULL] Please pull my kvm-ppc-next-5.7-1 tag Paul Mackerras
2020-03-30 23:08 ` Paul Mackerras
2020-03-31 14:47 ` Paolo Bonzini
2020-03-31 14:47   ` Paolo Bonzini
2020-01-21  3:33 [GIT PULL] Please pull my kvm-ppc-next-5.6-1 tag Paul Mackerras
2020-01-21  3:33 ` Paul Mackerras
2020-01-21 16:15 ` Paolo Bonzini
2020-01-21 16:15   ` Paolo Bonzini
2019-11-25  0:58 [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag Paul Mackerras
2019-11-25  0:58 ` Paul Mackerras
2019-11-25 10:29 ` Paolo Bonzini
2019-11-25 10:29   ` Paolo Bonzini
2019-11-25 23:44   ` Paul Mackerras
2019-11-25 23:44     ` Paul Mackerras
2019-11-26  8:52     ` Paolo Bonzini
2019-11-26  8:52       ` Paolo Bonzini
2019-10-31 11:13 [GIT PULL] Please pull my kvm-ppc-next-5.5-1 tag Paul Mackerras
2019-10-31 11:13 ` Paul Mackerras
2019-10-31 23:36 ` Paolo Bonzini
2019-10-31 23:36   ` Paolo Bonzini
2019-08-28 23:23 [GIT PULL] Please pull my kvm-ppc-next-5.4-1 tag Paul Mackerras
2019-08-28 23:23 ` Paul Mackerras
2019-09-06 12:04 ` Paul Mackerras
2019-09-06 12:04   ` Paul Mackerras
2019-09-10 14:51   ` Paolo Bonzini
2019-09-10 14:51     ` Paolo Bonzini
2019-05-14 10:13 [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag Paul Mackerras
2019-05-14 10:13 ` Paul Mackerras
2019-05-15 21:40 ` Paolo Bonzini
2019-05-15 21:40   ` Paolo Bonzini
2019-05-02  4:06 [GIT PULL] Please pull my kvm-ppc-next-5.2-1 tag Paul Mackerras
2019-05-02  4:06 ` Paul Mackerras
2019-05-09 22:46 ` Paul Mackerras
2019-05-09 22:46   ` Paul Mackerras
2019-02-22  5:14 [GIT PULL] Please pull my kvm-ppc-next-5.1-1 tag Paul Mackerras
2019-02-22  5:23 ` Masahiro Yamada
2019-02-22  5:52 ` Paul Mackerras
2019-02-22  6:46 ` Masahiro Yamada
2019-02-22  9:46 ` Paul Mackerras
2019-02-22 16:43 ` Paolo Bonzini
2019-03-01  3:37 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-2 tag Paul Mackerras
2019-03-01  5:21 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-3 tag Paul Mackerras
2019-03-14  3:31 ` Paul Mackerras
2019-03-15 18:13 ` 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=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 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.