From: Dongsheng Yang <dongsheng.yang@linux.dev>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Device Mapper <dm-devel@lists.linux.dev>
Cc: Zheng Gu <cengku@gmail.com>, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH 0/3] Documentation fixes for dm-pcache
Date: Fri, 15 Aug 2025 21:00:29 +0800 [thread overview]
Message-ID: <0b01e47c-ee81-4650-af5d-328544089391@linux.dev> (raw)
In-Reply-To: <20250815075622.23953-2-bagasdotme@gmail.com>
Acked-by: Dongsheng Yang <dongsheng.yang@linux.dev>
在 8/15/2025 3:56 PM, Bagas Sanjaya 写道:
> Hi,
>
> Here are docs fixes for dm-pcache as reported in linux-next ([1], [2]).
>
> Enjoy!
>
> [1]: https://lore.kernel.org/linux-next/20250815130543.3112144e@canb.auug.org.au/
> [2]: https://lore.kernel.org/linux-next/20250815131115.45518c74@canb.auug.org.au/
>
> Bagas Sanjaya (3):
> dm-pcache: Remove unnecessary line breaks
> dm-pcache: Use bullet list for data_crc constructor argument
> Documentation: device-mapper: Add dm-pcache docs to toctree index
>
> .../admin-guide/device-mapper/dm-pcache.rst | 15 ++++-----------
> Documentation/admin-guide/device-mapper/index.rst | 1 +
> 2 files changed, 5 insertions(+), 11 deletions(-)
>
>
> base-commit: 6fb8fbbaf147fe4153177320ee354c457605800a
next prev parent reply other threads:[~2025-08-15 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 7:56 [PATCH 0/3] Documentation fixes for dm-pcache Bagas Sanjaya
2025-08-15 7:56 ` [PATCH 1/3] dm-pcache: Remove unnecessary line breaks Bagas Sanjaya
2025-08-15 7:56 ` [PATCH 2/3] dm-pcache: Use bullet list for data_crc constructor argument Bagas Sanjaya
2025-08-15 7:56 ` [PATCH 3/3] Documentation: device-mapper: Add dm-pcache docs to toctree index Bagas Sanjaya
2025-08-15 13:00 ` Dongsheng Yang [this message]
2025-08-15 17:20 ` [PATCH 0/3] Documentation fixes for dm-pcache Randy Dunlap
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=0b01e47c-ee81-4650-af5d-328544089391@linux.dev \
--to=dongsheng.yang@linux.dev \
--cc=agk@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=cengku@gmail.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.