From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sean Christopherson <seanjc@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
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 kvm-x86 tree
Date: Fri, 27 Jun 2025 17:51:52 +1000 [thread overview]
Message-ID: <20250627175152.1f66c39b@canb.auug.org.au> (raw)
In-Reply-To: <aF1ty7P9MnQK7UPr@google.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
Hi Sean,
On Thu, 26 Jun 2025 08:56:59 -0700 Sean Christopherson <seanjc@google.com> wrote:
>
> On Thu, Jun 26, 2025, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the kvm-x86 tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/virt/kvm/x86/intel-tdx.rst:232: WARNING: Title underline too short.
> >
> > KVM_TDX_TERMINATE_VM
> > ------------------- [docutils]
> >
> > Introduced by commit
> >
> > 111a7311a016 ("KVM: TDX: Add sub-ioctl KVM_TDX_TERMINATE_VM")
>
> Fixed (assuming I didn't botch the fixup). Thanks Stephen!
Looks good, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-27 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 7:10 linux-next: build warning after merge of the kvm-x86 tree Stephen Rothwell
2025-06-26 15:56 ` Sean Christopherson
2025-06-27 7:51 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-14 7:14 Stephen Rothwell
2025-02-14 14:55 ` Sean Christopherson
2023-01-20 2:09 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=20250627175152.1f66c39b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=seanjc@google.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