From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH 2/9] block: cleanup the !zoned case in blk_revalidate_disk_zones
Date: Fri, 8 Nov 2019 18:50:22 +0000 [thread overview]
Message-ID: <DM6PR04MB5754E84538F2E0AC9C3FD797867B0@DM6PR04MB5754.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20191108015702.233102-3-damien.lemoal@wdc.com
Looks good to me.
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
On 11/07/2019 05:57 PM, Damien Le Moal wrote:
> From: Christoph Hellwig<hch@lst.de>
>
> blk_revalidate_disk_zones is never called for non-zoned devices. Just
> return early and warn instead of trying to handle this case.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
> Signed-off-by: Damien Le Moal<damien.lemoal@wdc.com>
> ---
next prev parent reply other threads:[~2019-11-08 18:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 1:56 [PATCH 0/9] Zoned block device enhancements and zone report rework Damien Le Moal
2019-11-08 1:56 ` [PATCH 1/9] block: Enhance blk_revalidate_disk_zones() Damien Le Moal
2019-11-08 6:28 ` [dm-devel] " Christoph Hellwig
2019-11-08 7:10 ` Hannes Reinecke
2019-11-08 1:56 ` [PATCH 2/9] block: cleanup the !zoned case in blk_revalidate_disk_zones Damien Le Moal
2019-11-08 7:11 ` Hannes Reinecke
2019-11-08 18:50 ` Chaitanya Kulkarni [this message]
2019-11-08 1:56 ` [PATCH 3/9] block: Simplify report zones execution Damien Le Moal
2019-11-08 7:12 ` Hannes Reinecke
2019-11-08 1:56 ` [PATCH 4/9] block: Remove partition support for zoned block devices Damien Le Moal
2019-11-08 6:30 ` [dm-devel] " Christoph Hellwig
2019-11-08 7:17 ` Hannes Reinecke
2019-11-08 7:28 ` Damien Le Moal
2019-11-08 1:56 ` [PATCH 5/9] null_blk: clean up the block device operations Damien Le Moal
2019-11-08 7:17 ` Hannes Reinecke
2019-11-08 18:47 ` Chaitanya Kulkarni
2019-11-08 1:56 ` [PATCH 6/9] null_blk: clean up report zones Damien Le Moal
2019-11-08 7:18 ` Hannes Reinecke
2019-11-08 18:47 ` Chaitanya Kulkarni
2019-11-08 1:57 ` [PATCH 7/9] null_blk: Add zone_nr_conv to features Damien Le Moal
2019-11-08 7:18 ` Hannes Reinecke
2019-11-08 18:48 ` Chaitanya Kulkarni
2019-11-08 1:57 ` [PATCH 8/9] scsi: sd_zbc: Cleanup sd_zbc_alloc_report_buffer() Damien Le Moal
2019-11-08 6:31 ` [dm-devel] " Christoph Hellwig
2019-11-08 7:20 ` Hannes Reinecke
2019-11-08 19:06 ` [dm-devel] " Bart Van Assche
2019-11-09 2:54 ` Damien Le Moal
2019-11-09 3:02 ` Bart Van Assche
2019-11-08 1:57 ` [PATCH 9/9] block: rework zone reporting Damien Le Moal
2019-11-08 7:23 ` Hannes Reinecke
2019-11-08 15:16 ` Mike Snitzer
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=DM6PR04MB5754E84538F2E0AC9C3FD797867B0@DM6PR04MB5754.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=snitzer@redhat.com \
--cc=yuchao0@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;
as well as URLs for NNTP newsgroup(s).