From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jeff Layton <jlayton@kernel.org>
Cc: 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 Linus' tree
Date: Tue, 5 Oct 2021 20:18:51 +1100 [thread overview]
Message-ID: <20211005201851.38832f67@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
Hi all,
In Linus' tree, today's linux-next build (htmldocs) produced this warning:
Documentation/filesystems/index.rst:18: WARNING: toctree contains reference to nonexisting document 'filesystems/mandatory-locking'
Introduced by commit
f7e33bdbd6d1 ("fs: remove mandatory file locking support")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-10-05 9:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 9:18 Stephen Rothwell [this message]
2021-10-05 10:10 ` linux-next: build warning after merge of Linus' tree Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2025-11-27 2:10 Stephen Rothwell
2025-12-16 1:08 ` Stephen Rothwell
2025-04-22 10:47 Stephen Rothwell
2025-04-22 15:59 ` Linus Torvalds
2025-04-22 17:50 ` Thomas Weißschuh
2025-04-22 18:20 ` Linus Torvalds
2025-04-22 20:48 ` Nathan Chancellor
2025-04-22 20:49 ` Linus Torvalds
2025-04-27 11:42 ` David Laight
2025-04-22 23:55 ` Stephen Rothwell
2025-03-05 9:46 Stephen Rothwell
2024-10-01 3:47 Stephen Rothwell
2024-10-01 15:02 ` Christian Brauner
2024-03-13 4:04 Stephen Rothwell
2023-05-08 4:44 Stephen Rothwell
2023-05-08 6:28 ` Sakari Ailus
2021-11-23 5:29 Stephen Rothwell
2022-01-20 3:27 ` Stephen Rothwell
2021-10-01 7:18 Stephen Rothwell
2021-10-01 16:33 ` Eric Dumazet
2019-07-29 4:04 Stephen Rothwell
2019-07-29 6:58 ` Takashi Iwai
2019-07-29 7:03 ` Johannes Berg
2019-07-29 7:07 ` Takashi Iwai
2019-07-29 8:20 ` 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=20211005201851.38832f67@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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