From: Janosch Frank <frankja@linux.ibm.com>
To: Collin Walling <walling@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: pbonzini@redhat.com, borntraeger@de.ibm.com, david@redhat.com,
cohuck@redhat.com, imbrenda@linux.ibm.com,
heiko.carstens@de.ibm.com, gor@linux.ibm.com, thuth@redhat.com
Subject: Re: [PATCH v2 0/2] s390: Add API Docs for DIAGNOSE 0x318 and fix rst
Date: Fri, 26 Jun 2020 09:53:00 +0200 [thread overview]
Message-ID: <1c737c33-24e3-82c5-a514-3931e6f9bb5a@linux.ibm.com> (raw)
In-Reply-To: <20200625150724.10021-1-walling@linux.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 693 bytes --]
On 6/25/20 5:07 PM, Collin Walling wrote:
> Changelog:
>
> v2
>
> • Reworded patch 1 doc text
>
> • Added "Introduced in commit..." for rst fix patch
>
> • Added r-b's (thanks!)
>
> Adds documentation for the s390-specfic DIAGNOSE 0x318 instruction, as
> well as fixes some missing rst symbols for the neighboring entries.
>
> Suggested-by: Cornelia Huck <cohuck@redhat.com>
thanks, applied
>
> Collin Walling (2):
> docs: kvm: add documentation for KVM_CAP_S390_DIAG318
> docs: kvm: fix rst formatting
>
> Documentation/virt/kvm/api.rst | 27 ++++++++++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-06-26 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 15:07 [PATCH v2 0/2] s390: Add API Docs for DIAGNOSE 0x318 and fix rst Collin Walling
2020-06-25 15:07 ` [PATCH v2 1/2] docs: kvm: add documentation for KVM_CAP_S390_DIAG318 Collin Walling
2020-06-25 16:11 ` Cornelia Huck
2020-06-25 15:07 ` [PATCH v2 2/2] docs: kvm: fix rst formatting Collin Walling
2020-06-26 7:53 ` Janosch Frank [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=1c737c33-24e3-82c5-a514-3931e6f9bb5a@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox