From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Collin Walling <walling@linux.ibm.com>
Subject: [GIT PULL 0/1] KVM: s390: add documentation for KVM_CAP_S390_DIAG318 (5.9)
Date: Mon, 14 Sep 2020 10:22:14 +0200 [thread overview]
Message-ID: <20200914082215.6143-1-borntraeger@de.ibm.com> (raw)
Paolo,
one missing piece of documentation for the diag318 interface that was
added in 5.9-rc1.
The following changes since commit 37f66bbef0920429b8cb5eddba849ec4308a9f8e:
KVM: emulator: more strict rsm checks. (2020-09-12 12:22:55 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-5.9-1
for you to fetch changes up to f20d4e924b4465822c4a35290b85aadf88ddf466:
docs: kvm: add documentation for KVM_CAP_S390_DIAG318 (2020-09-14 09:08:10 +0200)
----------------------------------------------------------------
KVM: s390: add documentation for KVM_CAP_S390_DIAG318
diag318 code was merged in 5.9-rc1, let us add some
missing documentation
----------------------------------------------------------------
Collin Walling (1):
docs: kvm: add documentation for KVM_CAP_S390_DIAG318
Documentation/virt/kvm/api.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
next reply other threads:[~2020-09-14 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 8:22 Christian Borntraeger [this message]
2020-09-14 8:22 ` [GIT PULL 1/1] docs: kvm: add documentation for KVM_CAP_S390_DIAG318 Christian Borntraeger
2020-09-20 13:14 ` [GIT PULL 0/1] KVM: s390: add documentation for KVM_CAP_S390_DIAG318 (5.9) 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=20200914082215.6143-1-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=walling@linux.ibm.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.