From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v6 02/10] block: refactor blk_revalidate_disk_zones()
Date: Wed, 21 Oct 2026 11:41:11 +0200 [thread overview]
Message-ID: <be5404ab-459e-445f-8488-4d087fb9352a@suse.de> (raw)
In-Reply-To: <20261013122750.2237843-3-dlemoal@kernel.org>
On 10/13/26 2:27 PM, Damien Le Moal wrote:
> Split out most of the code of blk_revalidate_disk_zones() into the
> internal function disk_revalidate_zones(). This will allow calling this
> new helper together with other code under the zone revalidation mutex.
> No functional change.
>
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-zoned.c | 63 +++++++++++++++++++++++++----------------------
> 1 file changed, 34 insertions(+), 29 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@kernel.org>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-10-21 9:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 12:27 [PATCH v6 00/10] Add support for storage element depopulation Damien Le Moal
2026-10-13 12:27 ` [PATCH v6 01/10] block: introduce disk_zone_is_offline() Damien Le Moal
2026-10-21 9:36 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 02/10] block: refactor blk_revalidate_disk_zones() Damien Le Moal
2026-10-21 9:41 ` Hannes Reinecke [this message]
2026-10-13 12:27 ` [PATCH v6 03/10] block: introduce storage element management Damien Le Moal
2026-10-13 14:14 ` Christoph Hellwig
2026-10-21 9:42 ` Hannes Reinecke
2026-10-21 9:59 ` Damien Le Moal
2026-10-21 10:49 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 04/10] block: add storage element management ioctls Damien Le Moal
2026-10-13 14:16 ` Christoph Hellwig
2026-10-21 9:45 ` Hannes Reinecke
2026-10-21 9:48 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 05/10] zloop: avoid potential wp_lock deadlocks Damien Le Moal
2026-10-13 14:17 ` Christoph Hellwig
2026-10-21 9:46 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 06/10] zloop: add storage element emulation Damien Le Moal
2026-10-13 14:17 ` Christoph Hellwig
2026-10-21 9:47 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 07/10] zloop: add degrade_element control command Damien Le Moal
2026-10-21 9:51 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 08/10] scsi: sd: fail read commands to offline zones early Damien Le Moal
2026-10-21 9:51 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 09/10] scsi: sd_zbc: always revalidate zones for disks supporting head depopulation Damien Le Moal
2026-10-13 14:17 ` Christoph Hellwig
2026-10-21 9:52 ` Hannes Reinecke
2026-10-13 12:27 ` [PATCH v6 10/10] scsi: sd_zbc: define storage element management operations Damien Le Moal
2026-10-21 9:53 ` Hannes Reinecke
2026-10-14 3:49 ` [PATCH v6 00/10] Add support for storage element depopulation Martin K. Petersen
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=be5404ab-459e-445f-8488-4d087fb9352a@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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