From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alasdair G Kergon <agk@redhat.com>, Mike Snitzer <snitzer@kernel.org>
Cc: "J. corwin Coburn" <corwin@hurlbutnet.net>,
Matthew Sakai <msakai@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the device-mapper tree
Date: Thu, 8 Feb 2024 14:42:18 +1100 [thread overview]
Message-ID: <20240208144218.09346f4d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi all,
After merging the device-mapper tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/admin-guide/device-mapper/vdo.rst: WARNING: document isn't included in any toctree
Documentation/admin-guide/device-mapper/vdo-design.rst: WARNING: document isn't included in any toctree
Introduced by commit
7903d6d10204 ("dm: add documentation for dm-vdo target")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-08 3:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:42 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-21 7:34 linux-next: build warning after merge of the device-mapper tree Stephen Rothwell
2021-08-10 9:31 ` Stephen Rothwell
2021-01-22 6:56 Stephen Rothwell
2020-07-09 3:26 Stephen Rothwell
2020-07-09 4:38 ` yangerkun
2019-02-20 2:15 Stephen Rothwell
2019-02-20 3:35 ` Mike Snitzer
2018-09-18 1:53 Stephen Rothwell
2017-12-11 2:05 Stephen Rothwell
2017-12-11 5:24 ` Mike Snitzer
2017-12-11 5:43 ` 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=20240208144218.09346f4d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agk@redhat.com \
--cc=corwin@hurlbutnet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=msakai@redhat.com \
--cc=snitzer@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).