From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: [GIT PULL 0/1] KVM: s390: Fix lockdep issue in vm memop
Date: Mon, 2 May 2022 17:30:52 +0200 [thread overview]
Message-ID: <20220502153053.6460-1-borntraeger@linux.ibm.com> (raw)
Paolo,
one patch that is sitting already too long in my tree (sorry, was out of
office some days).
The following changes since commit 3bcc372c9865bec3ab9bfcf30b2426cf68bc18af:
KVM: s390: selftests: Add error memop tests (2022-03-14 16:12:27 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-5.18-1
for you to fetch changes up to 4aa5ac75bf79cbbc46369163eb2e3addbff0d434:
KVM: s390: Fix lockdep issue in vm memop (2022-03-23 10:41:04 +0100)
----------------------------------------------------------------
KVM: s390: fix lockdep warning in new MEMOP call
----------------------------------------------------------------
Janis Schoetterl-Glausch (1):
KVM: s390: Fix lockdep issue in vm memop
arch/s390/kvm/kvm-s390.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
next reply other threads:[~2022-05-02 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 15:30 Christian Borntraeger [this message]
2022-05-02 15:30 ` [GIT PULL 1/1] KVM: s390: Fix lockdep issue in vm memop Christian Borntraeger
2022-05-02 15:39 ` [GIT PULL 0/1] " Paolo Bonzini
2022-05-02 15:41 ` Christian Borntraeger
2022-05-02 17:58 ` Heiko Carstens
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=20220502153053.6460-1-borntraeger@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=scgl@linux.ibm.com \
--cc=thuth@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