From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Bernd Schubert <bschubert@ddn.com>,
Miklos Szeredi <mszeredi@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the fuse tree
Date: Tue, 21 Jan 2025 17:48:48 +1100 [thread overview]
Message-ID: <20250121174848.382cc2c6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi all,
After merging the fuse tree, today's linux-next build (htmldocs) produced
these warnings:
/home/sfr/next/next/Documentation/filesystems/fuse-io-uring.rst:19: ERROR: Unexpected indentation. [docutils]
/home/sfr/next/next/Documentation/filesystems/fuse-io-uring.rst:46: WARNING: Inline substitution_reference start-string without end-string. [docutils]
/home/sfr/next/next/Documentation/filesystems/fuse-io-uring.rst:53: WARNING: Inline substitution_reference start-string without end-string. [docutils]
/home/sfr/next/next/Documentation/filesystems/fuse-io-uring.rst:65: WARNING: Inline substitution_reference start-string without end-string. [docutils]
/home/sfr/next/next/Documentation/filesystems/fuse-io-uring.rst:94: WARNING: Inline substitution_reference start-string without end-string. [docutils]
/home/sfr/next/next/Documentation/filesystems/fuse-io-uring.rst:95: WARNING: Inline substitution_reference start-string without end-string. [docutils]
Introduced by commit
3d75eb0c9c67 ("fuse: Add fuse-io-uring design documentation")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-01-21 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 6:48 Stephen Rothwell [this message]
2025-01-21 8:37 ` [PATCH] fuse: Fix Documentation/filesystems/fuse-io-uring.rst Bernd Schubert
2025-01-21 9:27 ` Miklos Szeredi
2025-01-21 11:15 ` Bernd Schubert
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=20250121174848.382cc2c6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bschubert@ddn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.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