From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kent Overstreet <kent.overstreet@linux•dev>
Cc: Joshua Ashton <joshua@froggi•es>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the bcachefs tree
Date: Fri, 21 Feb 2025 16:21:35 +1100 [thread overview]
Message-ID: <20250221162135.79be0147@canb.auug.org.au> (raw)
In-Reply-To: <20250221161911.2d16138b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
Hi all,
On Fri, 21 Feb 2025 16:19:11 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the bcachefs tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/filesystems/bcachefs/casefolding.rst:84: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
>
> Introduced by commit
>
> bc5cc09246c5 ("bcachefs: bcachefs_metadata_version_casefolding")
Also:
Documentation/filesystems/bcachefs/casefolding.rst:36: WARNING: Inline interpreted text or phrase reference start-string without end-string. [docutils]
Documentation/filesystems/bcachefs/casefolding.rst:75: WARNING: Title underline too short.
dentry/dcache considerations
--------- [docutils]
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-21 5:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 5:19 linux-next: build warning after merge of the bcachefs tree Stephen Rothwell
2025-02-21 5:21 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-17 6:28 Stephen Rothwell
2025-02-21 5:17 Stephen Rothwell
2025-02-04 3:12 Stephen Rothwell
2024-07-18 5:46 Stephen Rothwell
2024-05-01 5:16 Stephen Rothwell
2024-02-26 6:46 Stephen Rothwell
2024-01-17 2:28 Stephen Rothwell
2023-11-26 22:46 Stephen Rothwell
2023-09-12 5:02 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=20250221162135.79be0147@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=joshua@froggi$(echo .)es \
--cc=kent.overstreet@linux$(echo .)dev \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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