From: Mikulas Patocka <mpatocka@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Dongsheng Yang <dongsheng.yang@linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the device-mapper tree
Date: Fri, 15 Aug 2025 17:21:07 +0200 (CEST) [thread overview]
Message-ID: <1a59c25e-c9d1-f90a-2911-31f921d0b69b@redhat.com> (raw)
In-Reply-To: <20250815130543.3112144e@canb.auug.org.au>
Hi
I've fixed the documentation indentations and folded it into the existing
commit in the linux-dm git.
Mikulas
On Fri, 15 Aug 2025, Stephen Rothwell wrote:
> Hi all,
>
> After merging the device-mapper tree, today's linux-next build (htmldocs)
> failed like this:
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage: Documentation/admin-guide/device-mapper/dm-pcache.rst:27: (SEVERE/4) Title overline & underline mismatch.
>
> -------------------------------------------------------------------------------
> Constructor
> ===========
>
> Caused by commit
>
> 6fb8fbbaf147 ("dm-pcache: add persistent cache target in device-mapper")
>
> I have applied the following fix patch for today (there may be better).
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 15 Aug 2025 13:01:51 +1000
> Subject: [PATCH] fix up for "dm-pcache: add persistent cache target in
> device-mapper"
>
> Sphinx parallel build error:
> docutils.utils.SystemMessage: Documentation/admin-guide/device-mapper/dm-pcache.rst:27: (SEVERE/4) Title overline & underline mismatch.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> Documentation/admin-guide/device-mapper/dm-pcache.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/admin-guide/device-mapper/dm-pcache.rst b/Documentation/admin-guide/device-mapper/dm-pcache.rst
> index e6433fab7bd6..550026219a6f 100644
> --- a/Documentation/admin-guide/device-mapper/dm-pcache.rst
> +++ b/Documentation/admin-guide/device-mapper/dm-pcache.rst
> @@ -25,6 +25,7 @@ Quick feature summary
> * *Log-structured write-back* that preserves backend crash-consistency
>
> -------------------------------------------------------------------------------
> +
> Constructor
> ===========
>
> @@ -58,6 +59,7 @@ The first time a pmem device is used, dm-pcache formats it automatically
> (super-block, cache_info, etc.).
>
> -------------------------------------------------------------------------------
> +
> Status line
> ===========
>
> @@ -98,6 +100,7 @@ Field meanings
> =============================== =============================================
>
> -------------------------------------------------------------------------------
> +
> Messages
> ========
>
> @@ -108,6 +111,7 @@ Messages
> dmsetup message <dev> 0 gc_percent <0-90>
>
> -------------------------------------------------------------------------------
> +
> Theory of operation
> ===================
>
> @@ -152,6 +156,7 @@ range when it is inserted and stores it in the on-media key. Reads
> validate the CRC before copying to the caller.
>
> -------------------------------------------------------------------------------
> +
> Failure handling
> ================
>
> @@ -164,6 +169,7 @@ Failure handling
> use-after-free keys.
>
> -------------------------------------------------------------------------------
> +
> Limitations & TODO
> ==================
>
> @@ -173,6 +179,7 @@ Limitations & TODO
> * Discard planned.
>
> -------------------------------------------------------------------------------
> +
> Example workflow
> ================
>
> @@ -197,5 +204,6 @@ Example workflow
> dmsetup remove pcache_sdb
>
> -------------------------------------------------------------------------------
> +
> ``dm-pcache`` is under active development; feedback, bug reports and patches
> are very welcome!
> --
> 2.50.1
>
> --
> Cheers,
> Stephen Rothwell
>
next prev parent reply other threads:[~2025-08-15 15:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 3:05 linux-next: build failure after merge of the device-mapper tree Stephen Rothwell
2025-08-15 8:05 ` Bagas Sanjaya
2025-08-15 15:21 ` Mikulas Patocka [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-10 2:20 Stephen Rothwell
2024-02-07 3:40 Stephen Rothwell
2024-02-07 3:54 ` Matthew Sakai
2024-02-07 15:47 ` Mike Snitzer
2023-09-15 0:06 Stephen Rothwell
2023-06-23 4:30 Stephen Rothwell
2023-06-23 16:47 ` Demi Marie Obenour
2021-02-11 3:36 Stephen Rothwell
2021-02-11 14:37 ` Mike Snitzer
2020-04-22 2:54 Stephen Rothwell
2018-12-06 6:21 Stephen Rothwell
2018-12-06 13:41 ` Mike Snitzer
2018-12-06 20:23 ` Stephen Rothwell
2018-05-31 4:23 Stephen Rothwell
2018-05-31 4:35 ` Jens Axboe
2018-05-31 4:38 ` Stephen Rothwell
2018-05-31 12:10 ` Mike Snitzer
2018-05-31 14:20 ` Jens Axboe
2018-05-31 14:22 ` Jens Axboe
2018-05-31 15:02 ` Jens Axboe
2018-05-31 21:42 ` Stephen Rothwell
2018-03-27 2:39 Stephen Rothwell
2018-03-27 15:39 ` Bart Van Assche
2017-06-19 2:27 Stephen Rothwell
2017-06-09 3:12 Stephen Rothwell
2017-06-09 4:28 ` Damien Le Moal
2017-06-09 11:59 ` Mike Snitzer
2016-03-04 2:59 Stephen Rothwell
2016-03-04 3:14 ` Mike Snitzer
2015-11-01 10:43 Stephen Rothwell
2015-11-01 13:44 ` Mike Snitzer
2015-07-05 23:27 Stephen Rothwell
2015-05-22 3:27 Stephen Rothwell
2015-05-22 12:49 ` Mike Snitzer
2015-05-22 13:26 ` Mike Snitzer
2015-05-22 14:58 ` Jens Axboe
2014-01-15 3:52 Stephen Rothwell
2014-01-15 4:30 ` Mike Snitzer
2013-11-05 2:51 Stephen Rothwell
2013-11-05 3:20 ` Mike Snitzer
2013-11-05 3:32 ` Stephen Rothwell
2013-11-05 12:54 ` Mike Snitzer
2013-11-05 16:22 ` Jens Axboe
2013-11-05 22:42 ` Stephen Rothwell
2013-11-05 22:44 ` Jens Axboe
2010-08-02 1:31 Stephen Rothwell
2010-08-02 6:44 ` Milan Broz
2010-08-02 11:34 ` Alasdair G Kergon
2010-06-30 2:57 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=1a59c25e-c9d1-f90a-2911-31f921d0b69b@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=dongsheng.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).