From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
drbd-dev@lists.linbit.com, Zhang Yi <yi.zhang@huaweicloud.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
john.g.garry@oracle.com, pmenzel@molgen.mpg.de, hch@lst.de,
martin.petersen@oracle.com, yi.zhang@huawei.com,
yukuai3@huawei.com, yangerkun@huawei.com
Subject: Re: (subset) [PATCH v2 0/2] Fix the initialization of max_hw_wzeroes_unmap_sectors for stacking drivers
Date: Wed, 17 Sep 2025 08:21:11 -0600 [thread overview]
Message-ID: <175811887192.378805.895284774096542580.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250910111107.3247530-1-yi.zhang@huaweicloud.com>
On Wed, 10 Sep 2025 19:11:05 +0800, Zhang Yi wrote:
> Changes since v1:
> - Improve commit messages in patch 1 by adding a simple reproduction
> case as Paul suggested and explaining the implementation differences
> between RAID 0 and RAID 1/10/5, no code changes.
>
> v1: https://lore.kernel.org/linux-block/20250825083320.797165-1-yi.zhang@huaweicloud.com/
>
> [...]
Applied, thanks!
[2/2] drbd: init queue_limits->max_hw_wzeroes_unmap_sectors parameter
commit: 027a7a9c07d0d759ab496a7509990aa33a4b689c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-09-17 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 11:11 [PATCH v2 0/2] Fix the initialization of max_hw_wzeroes_unmap_sectors for stacking drivers Zhang Yi
2025-09-10 11:11 ` [PATCH v2 1/2] md: init queue_limits->max_hw_wzeroes_unmap_sectors parameter Zhang Yi
2025-09-10 11:41 ` Hannes Reinecke
2025-09-17 1:20 ` Yu Kuai
2025-09-10 11:11 ` [PATCH v2 2/2] drbd: " Zhang Yi
2025-09-10 11:41 ` Hannes Reinecke
2025-09-12 6:16 ` [PATCH v2 0/2] Fix the initialization of max_hw_wzeroes_unmap_sectors for stacking drivers Zhang Yi
2025-09-15 10:43 ` John Garry
2025-09-16 0:49 ` Yu Kuai
2025-09-17 14:21 ` Jens Axboe [this message]
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=175811887192.378805.895284774096542580.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pmenzel@molgen.mpg.de \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yukuai3@huawei.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