From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anna Schumaker <anna@kernel.org>, Trond Myklebust <trondmy@gmail.com>
Cc: Anna Schumaker <anna.schumaker@oracle.com>,
Mike Snitzer <snitzer@kernel.org>,
NFS Mailing List <linux-nfs@vger.kernel.org>,
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 nfs-anna tree
Date: Tue, 24 Sep 2024 14:46:26 +1000 [thread overview]
Message-ID: <20240924144626.3b374ff3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Hi all,
After merging the nfs-anna tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/filesystems/nfs/localio.rst:43: ERROR: Unexpected indentation.
Documentation/filesystems/nfs/localio.rst:56: ERROR: Unexpected indentation.
Documentation/filesystems/nfs/localio.rst:179: WARNING: Inline emphasis start-string without end-string.
Documentation/filesystems/nfs/localio.rst:190: WARNING: Definition list ends without a blank line; unexpected unindent.
Documentation/filesystems/nfs/localio.rst:191: WARNING: Definition list ends without a blank line; unexpected unindent.
Documentation/filesystems/nfs/localio.rst: WARNING: document isn't included in any toctree
Introduced by commit
92945bd81ca4 ("nfs: add Documentation/filesystems/nfs/localio.rst")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-09-24 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 4:46 Stephen Rothwell [this message]
2024-09-24 17:08 ` linux-next: build warning after merge of the nfs-anna tree Mike Snitzer
-- strict thread matches above, loose matches on Subject: below --
2025-01-09 4:23 Stephen Rothwell
2025-01-14 5:45 ` Stephen Rothwell
2018-07-30 8:52 Stephen Rothwell
2018-07-31 9:04 ` David Wysochanski
2018-07-31 13:46 ` Anna Schumaker
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=20240924144626.3b374ff3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=anna.schumaker@oracle.com \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=snitzer@kernel.org \
--cc=trondmy@gmail.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;
as well as URLs for NNTP newsgroup(s).