From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v3 0/5] Improve checks in blk_revalidate_disk_zones()
Date: Wed, 05 Jul 2023 22:04:39 -0400 [thread overview]
Message-ID: <yq1wmzdkd7u.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230703024812.76778-1-dlemoal@kernel.org> (Damien Le Moal's message of "Mon, 3 Jul 2023 11:48:07 +0900")
Damien,
> blk_revalidate_disk_zones() implements checks of the zones of a zoned
> block device, verifying that the zone size is a power of 2 number of
> sectors, that all zones (except possibly the last one) have the same
> size and that zones cover the entire addressing space of the device.
Applied to 6.5/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-07-06 2:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 2:48 [PATCH v3 0/5] Improve checks in blk_revalidate_disk_zones() Damien Le Moal
2023-07-03 2:48 ` [PATCH v3 1/5] scsi: sd_zbc: Set zone limits before revalidating zones Damien Le Moal
2023-07-03 7:23 ` Johannes Thumshirn
2023-07-03 2:48 ` [PATCH v3 2/5] nvme: zns: " Damien Le Moal
2023-07-03 7:23 ` Johannes Thumshirn
2023-07-03 2:48 ` [PATCH v3 3/5] block: nullblk: " Damien Le Moal
2023-07-03 7:24 ` Johannes Thumshirn
2023-07-03 2:48 ` [PATCH v3 4/5] block: virtio_blk: " Damien Le Moal
2023-07-03 7:24 ` Johannes Thumshirn
2023-07-03 2:48 ` [PATCH v3 5/5] block: improve checks in blk_revalidate_disk_zones() Damien Le Moal
2023-07-03 7:26 ` Johannes Thumshirn
2023-07-06 2:04 ` Martin K. Petersen [this message]
2023-07-11 16:31 ` [PATCH v3 0/5] Improve " 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=yq1wmzdkd7u.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox