linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Alasdair G Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>
Cc: Dongsheng Yang <dongsheng.yang@linux.dev>,
	Mikulas Patocka <mpatocka@redhat.com>,
	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 15:05:18 +0700	[thread overview]
Message-ID: <aJ7qPqOZuRLoLUnZ@archie.me> (raw)
In-Reply-To: <20250815130543.3112144e@canb.auug.org.au>

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

On Fri, Aug 15, 2025 at 01:05:43PM +1000, Stephen Rothwell wrote:
> 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
>  
>  -------------------------------------------------------------------------------
> +

I think these unnecessary line breaks can be trimmed instead ([1]).

Thanks.

[1]: https://lore.kernel.org/dm-devel/20250815075622.23953-3-bagasdotme@gmail.com/

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-08-15  8:05 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 [this message]
2025-08-15 15:21 ` Mikulas Patocka
  -- 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=aJ7qPqOZuRLoLUnZ@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=agk@redhat.com \
    --cc=dongsheng.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --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).