From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paolo Bonzini <pbonzini@redhat•com>, KVM <kvm@vger•kernel.org>
Cc: Binbin Wu <binbin.wu@linux•intel.com>,
Isaku Yamahata <isaku.yamahata@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 tree
Date: Fri, 16 May 2025 10:16:04 +1000 [thread overview]
Message-ID: <20250516101604.7261c44a@canb.auug.org.au> (raw)
In-Reply-To: <20250409131356.48683f58@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi all,
On Wed, 9 Apr 2025 13:13:56 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the kvm tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/virt/kvm/x86/intel-tdx.rst:255: WARNING: Footnote [1] is not referenced. [ref.footnote]
>
> Introduced by commit
>
> 52f52ea79a4c ("Documentation/virt/kvm: Document on Trust Domain Extensions (TDX)")
I am still seeing this warning (as of yesterday).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-16 0:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 3:13 linux-next: build warning after merge of the kvm tree Stephen Rothwell
2025-05-16 0:16 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-28 8:29 Stephen Rothwell
2024-11-13 6:29 ` Stephen Rothwell
2024-11-13 13:58 ` Sean Christopherson
2024-11-13 14:00 ` Paolo Bonzini
2024-09-23 3:45 Stephen Rothwell
2024-07-17 5:59 Stephen Rothwell
2024-07-30 10:11 ` Stephen Rothwell
2023-11-14 3:13 Stephen Rothwell
2023-11-14 12:50 ` Paolo Bonzini
2022-12-13 4:41 Stephen Rothwell
2022-12-13 5:11 ` Sean Christopherson
2022-06-27 8:19 Stephen Rothwell
2022-06-27 9:57 ` Bagas Sanjaya
2022-08-09 6:41 ` Stephen Rothwell
2022-01-10 8:58 Stephen Rothwell
2022-01-11 2:55 ` Wang, Wei W
2022-01-20 3:36 ` Stephen Rothwell
2022-01-20 5:52 ` Wang, Wei W
2021-04-22 8:53 Stephen Rothwell
2021-02-09 9:59 Stephen Rothwell
2021-02-09 10:01 ` Paolo Bonzini
2019-11-25 3:03 Stephen Rothwell
2013-01-10 2:34 Stephen Rothwell
2013-01-10 6:56 ` Gleb Natapov
2010-07-26 5:14 Stephen Rothwell
2010-05-27 4:53 Stephen Rothwell
2010-05-27 10:19 ` Roedel, Joerg
2010-05-27 10:49 ` Stephen Rothwell
2010-05-27 12:13 ` Avi Kivity
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=20250516101604.7261c44a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=binbin.wu@linux$(echo .)intel.com \
--cc=isaku.yamahata@intel$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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