From: Janosch Frank <frankja@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the kvms390 tree
Date: Fri, 21 Nov 2025 10:28:30 +0100 [thread overview]
Message-ID: <7fa3e596-aece-4375-a934-37e7d5bcc42b@linux.ibm.com> (raw)
In-Reply-To: <20251121160144.02cb92b3@canb.auug.org.au>
On 11/21/25 06:01, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvms390 tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/virt/kvm/api.rst:8754: WARNING: Title underline too short.
>
> 7.46 KVM_CAP_S390_USER_OPEREXEC
> ---------------------------- [docutils]
That is indeed too short.
Thanks for the info, I've fixed it up.
next prev parent reply other threads:[~2025-11-21 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 5:01 linux-next: build warning after merge of the kvms390 tree Stephen Rothwell
2025-11-21 9:28 ` Janosch Frank [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-11 10:55 Stephen Rothwell
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=7fa3e596-aece-4375-a934-37e7d5bcc42b@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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