From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Keith Busch <keith.busch@wdc.com>, Christoph Hellwig <hch@lst.de>,
dm-devel@lists.linux.dev, Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-xfs@vger.kernel.org,
Carlos Maiolino <cem@kernel.org>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: [PATCH v4 03/15] block: cleanup blkdev_report_zones()
Date: Wed, 5 Nov 2025 06:22:37 +0900 [thread overview]
Message-ID: <20251104212249.1075412-4-dlemoal@kernel.org> (raw)
In-Reply-To: <20251104212249.1075412-1-dlemoal@kernel.org>
The variable capacity is used only in one place and so can be removed
and get_capacity(disk) used directly instead.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
---
block/blk-zoned.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/block/blk-zoned.c b/block/blk-zoned.c
index 39381f2b2e94..345a99c0b031 100644
--- a/block/blk-zoned.c
+++ b/block/blk-zoned.c
@@ -161,7 +161,6 @@ int blkdev_report_zones(struct block_device *bdev, sector_t sector,
unsigned int nr_zones, report_zones_cb cb, void *data)
{
struct gendisk *disk = bdev->bd_disk;
- sector_t capacity = get_capacity(disk);
struct disk_report_zones_cb_args args = {
.disk = disk,
.user_cb = cb,
@@ -171,7 +170,7 @@ int blkdev_report_zones(struct block_device *bdev, sector_t sector,
if (!bdev_is_zoned(bdev) || WARN_ON_ONCE(!disk->fops->report_zones))
return -EOPNOTSUPP;
- if (!nr_zones || sector >= capacity)
+ if (!nr_zones || sector >= get_capacity(disk))
return 0;
return disk->fops->report_zones(disk, sector, nr_zones,
--
2.51.0
next prev parent reply other threads:[~2025-11-04 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 21:22 [PATCH v4 00/15] Introduce cached report zones Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 01/15] block: handle zone management operations completions Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 02/15] block: freeze queue when updating zone resources Damien Le Moal
2025-11-04 21:22 ` Damien Le Moal [this message]
2025-11-04 21:22 ` [PATCH v4 04/15] block: introduce disk_report_zone() Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 05/15] block: reorganize struct blk_zone_wplug Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 06/15] block: use zone condition to determine conventional zones Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 07/15] block: track zone conditions Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 08/15] block: refactor blkdev_report_zones() code Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 09/15] block: introduce blkdev_get_zone_info() Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 10/15] block: introduce blkdev_report_zones_cached() Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 11/15] block: introduce BLKREPORTZONESV2 ioctl Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 12/15] block: improve zone_wplugs debugfs attribute output Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 13/15] block: add zone write plug condition to debugfs zone_wplugs Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 14/15] btrfs: use blkdev_report_zones_cached() Damien Le Moal
2025-11-04 21:22 ` [PATCH v4 15/15] xfs: " Damien Le Moal
2025-11-05 3:56 ` [PATCH v4 00/15] Introduce cached report zones Martin K. Petersen
2025-11-05 15:45 ` 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=20251104212249.1075412-4-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=cem@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=keith.busch@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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 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).