All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
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 the fscache tree
Date: Wed, 3 Mar 2021 17:07:43 +1100	[thread overview]
Message-ID: <20210303170743.69ceaeb8@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

Hi all,

After merging the fscache tree, today's linux-next build (htmldocs)
produced this warning:

Documentation/filesystems/netfs_library.rst: WARNING: document isn't included in any toctree

Introduced by commit

  cefbac2d6fc5 ("netfs: Documentation for helper library")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-03-03 12:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  6:07 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-03  9:28 linux-next: build warning after merge of the fscache tree Stephen Rothwell
2021-12-20 11:46 Stephen Rothwell
2021-11-30  5:23 Stephen Rothwell
2021-11-30  6:51 ` Stephen Rothwell
2021-11-30 11:13 ` David Howells
2021-11-30 11:18 ` David Howells
2021-11-30  4:27 Stephen Rothwell
2021-12-06  7:08 ` Stephen Rothwell
2021-10-05  9:46 Stephen Rothwell
2021-10-21  1:29 ` Stephen Rothwell
2021-10-21 14:32 ` David Howells
2021-10-21 23:15   ` Stephen Rothwell
2021-03-02 22:16 Stephen Rothwell
2021-03-02 22:48 ` David Howells

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=20210303170743.69ceaeb8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.