From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH 2/3] block: Rename disk_set_zoned()
Date: Tue, 5 Mar 2024 08:41:36 +0900 [thread overview]
Message-ID: <ddf30983-0402-441c-9925-d37114c09e71@kernel.org> (raw)
In-Reply-To: <20240302140755.GB1319@lst.de>
On 3/2/24 23:07, Christoph Hellwig wrote:
> On Sat, Mar 02, 2024 at 04:26:38AM +0900, Damien Le Moal wrote:
>> The disk_set_zoned() function operates on the zoned request queue limit
>> of a block device and does not change anything to the gendisk of the
>> device. To reflect this behavior and to be consistent with other request
>> queue limit setting functions, rename disk_set_zoned() to
>> blk_queue_zoned().
>
> Can we just hold this off a bit? I have the big nvme queue limits series
> that removes the zns usage, and early next merge window scsi will be
> converted as well and this function will go away entirely.
I suspected as much, but sent the patches anyway.. Fine with me !
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-03-04 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 19:26 [PATCH 0/3] queue limits cleanup Damien Le Moal
2024-03-01 19:26 ` [PATCH 1/3] virtio_blk: Do not use disk_set_max_open/active_zones() Damien Le Moal
2024-03-02 14:06 ` Christoph Hellwig
2024-03-04 7:49 ` Johannes Thumshirn
2024-03-01 19:26 ` [PATCH 2/3] block: Rename disk_set_zoned() Damien Le Moal
2024-03-02 14:07 ` Christoph Hellwig
2024-03-04 23:41 ` Damien Le Moal [this message]
2024-03-01 19:26 ` [PATCH 3/3] block: Rename disk_set_max_open/active_zones() Damien Le Moal
2024-03-02 14:08 ` Christoph Hellwig
2024-03-06 15:35 ` (subset) [PATCH 0/3] queue limits cleanup 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=ddf30983-0402-441c-9925-d37114c09e71@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.