[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78730bd4-a184-e0f0-4634-d09dbaf59958@acm.org>
Date: Tue, 3 May 2022 09:54:13 -0700
From: Bart Van Assche <bvanassche@....org>
To: Pankaj Raghav <p.raghav@...sung.com>, jaegeuk@...nel.org,
axboe@...nel.dk, snitzer@...nel.org, hch@....de, mcgrof@...nel.org,
naohiro.aota@....com, sagi@...mberg.me,
damien.lemoal@...nsource.wdc.com, dsterba@...e.com,
johannes.thumshirn@....com
Cc: linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
clm@...com, gost.dev@...sung.com, chao@...nel.org,
linux-f2fs-devel@...ts.sourceforge.net, josef@...icpanda.com,
jonathan.derrick@...ux.dev, agk@...hat.com, kbusch@...nel.org,
kch@...dia.com, linux-nvme@...ts.infradead.org,
dm-devel@...hat.com, jiangbo.365@...edance.com,
linux-fsdevel@...r.kernel.org, matias.bjorling@....com,
linux-block@...r.kernel.org
Subject: Re: [PATCH 06/16] nvmet: use blk_queue_zone_no()
On 4/27/22 09:02, Pankaj Raghav wrote:
> From: Luis Chamberlain <mcgrof@...nel.org>
>
> Instead of open coding the number of zones given a sector, use the helper
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I can't parse this. Please rephrase this.
> blk_queue_zone_no(). This let's us make modifications to the math if
> needed in one place and adds now support for npo2 zone devices.
But since the code looks fine:
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists