From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: [PATCH v2 0/3] Zone related cleanups
Date: Fri, 7 Nov 2025 15:38:41 +0900 [thread overview]
Message-ID: <20251107063844.151103-1-dlemoal@kernel.org> (raw)
3 more patches to go on top of the cached report zone support (and its
fixes from Christoph)..
The first one improves blk_zone_wp_offset(), the second patch refactors
the use of this function to simplify the code a little. The last patch
introduces bdev_zone_start() as a replacement to using ALIGN_DOWN() for
getting the start sector of a zone.
Changes from v1:
- Added patch 1
- Changed patch 2 to not open code blk_zone_wp_offset() in
disk_zone_wplug_sync_wp_offset().
- Added review tags to patch 3
Damien Le Moal (3):
block: improve blk_zone_wp_offset()
block: refactor disk_zone_wplug_sync_wp_offset()
block: introduce bdev_zone_start()
block/blk-zoned.c | 39 +++++++++++++++++++--------------------
include/linux/blkdev.h | 6 ++++++
2 files changed, 25 insertions(+), 20 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-07 6:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 6:38 Damien Le Moal [this message]
2025-11-07 6:38 ` [PATCH v2 1/3] block: improve blk_zone_wp_offset() Damien Le Moal
2025-11-07 8:34 ` Hannes Reinecke
2025-11-07 11:40 ` Christoph Hellwig
2025-11-07 16:06 ` Bart Van Assche
2025-11-07 6:38 ` [PATCH v2 2/3] block: refactor disk_zone_wplug_sync_wp_offset() Damien Le Moal
2025-11-07 8:35 ` Hannes Reinecke
2025-11-07 11:40 ` Christoph Hellwig
2025-11-07 16:06 ` Bart Van Assche
2025-11-07 6:38 ` [PATCH v2 3/3] block: introduce bdev_zone_start() Damien Le Moal
2025-11-07 8:36 ` Hannes Reinecke
2025-11-07 16:28 ` [PATCH v2 0/3] Zone related cleanups Jens Axboe
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=20251107063844.151103-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.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.