From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, linux-doc@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Pierre Morel <pmorel@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next 3/3] Documentation: kvm: extend KVM_S390_ZPCI_OP subheading underline
Date: Tue, 12 Jul 2022 11:38:35 +0200 [thread overview]
Message-ID: <8c7993c0-7c53-d609-c731-1c7c25e50a65@de.ibm.com> (raw)
In-Reply-To: <20220712092954.142027-4-bagasdotme@gmail.com>
Am 12.07.22 um 11:29 schrieb Bagas Sanjaya:
> Stephen Rothwell reported the htmldocs warning:
>
> Documentation/virt/kvm/api.rst:5959: WARNING: Title underline too short.
>
> 4.137 KVM_S390_ZPCI_OP
> --------------------
>
> The warning is due to subheading underline on KVM_S390_ZPCI_OP section is
> short of 2 dashes.
>
> Extend the underline to fix the warning.
>
> Link: https://lore.kernel.org/linux-next/20220711205557.183c3b14@canb.auug.org.au/
> Fixes: a0c4d1109d6cc5 ("KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Pierre Morel <pmorel@linux.ibm.com>
> Cc: Thomas Huth <thuth@redhat.com>
> Cc: Matthew Rosato <mjrosato@linux.ibm.com>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Janosch Frank <frankja@linux.ibm.com>
> Cc: kvm@vger.kernel.org
> Cc: linux-s390@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
will queue this on top of the kvms390 tree.
> ---
> Documentation/virt/kvm/api.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 1ae3508d51c537..e6bd6c6dbd13ec 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -5956,7 +5956,7 @@ KVM_PV_DUMP_CPU
> The length of the returned data is provided by uv_info.guest_cpu_stor_len.
>
> 4.137 KVM_S390_ZPCI_OP
> ---------------------
> +----------------------
>
> :Capability: KVM_CAP_S390_ZPCI_OP
> :Architectures: s390
prev parent reply other threads:[~2022-07-12 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 9:29 [PATCH next 0/3] miscellaneous documentation fixes for linux-next Bagas Sanjaya
2022-07-12 9:29 ` [PATCH next 1/3] Documentation: qat: Use code block for qat sysfs example Bagas Sanjaya
2022-07-12 11:32 ` Giovanni Cabiddu
2022-07-12 9:29 ` [PATCH next 2/3] Documentation: qat: rewrite description Bagas Sanjaya
2022-07-12 11:33 ` Giovanni Cabiddu
2022-07-12 21:54 ` Giovanni Cabiddu
2022-07-12 9:29 ` [PATCH next 3/3] Documentation: kvm: extend KVM_S390_ZPCI_OP subheading underline Bagas Sanjaya
2022-07-12 9:38 ` Christian Borntraeger [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=8c7993c0-7c53-d609-c731-1c7c25e50a65@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--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