From: Stefan Hajnoczi <stefanha@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Paolo Bonzini <pbonzini@redhat.com>,
Damien Le Moal <dlemoal@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
virtualization@lists.linux.dev, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/5] virtio_blk: cleanup zoned device probing
Date: Mon, 18 Dec 2023 10:13:30 -0500 [thread overview]
Message-ID: <20231218151330.GD12768@fedora> (raw)
In-Reply-To: <20231217165359.604246-2-hch@lst.de>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Sun, Dec 17, 2023 at 05:53:55PM +0100, Christoph Hellwig wrote:
> Move reading and checking the zoned model from virtblk_probe_zoned_device
> into the caller, leaving only the code to perform the actual setup for
> host managed zoned devices in virtblk_probe_zoned_device.
>
> This allows to share the model reading and sharing between builds with
> and without CONFIG_BLK_DEV_ZONED, and improve it for the
> !CONFIG_BLK_DEV_ZONED case.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/block/virtio_blk.c | 50 +++++++++++++++++---------------------
> 1 file changed, 22 insertions(+), 28 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-12-18 15:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 16:53 remove support for the host aware zoned model Christoph Hellwig
2023-12-17 16:53 ` [PATCH 1/5] virtio_blk: cleanup zoned device probing Christoph Hellwig
2023-12-18 9:35 ` Damien Le Moal
2023-12-18 15:13 ` Stefan Hajnoczi [this message]
2024-01-16 19:02 ` [f2fs-dev] " patchwork-bot+f2fs
2023-12-17 16:53 ` [PATCH 2/5] virtio_blk: remove the broken zone revalidation support Christoph Hellwig
2023-12-18 9:37 ` Damien Le Moal
2023-12-18 15:15 ` Stefan Hajnoczi
2023-12-17 16:53 ` [PATCH 3/5] block: remove support for the host aware zone model Christoph Hellwig
[not found] ` <b4d33dc359495c6227a3f20285566eed27718a14.camel@mediatek.com>
2023-12-18 6:53 ` Damien Le Moal
[not found] ` <f19c41b9ea990e6da734b6c81caeebb73fb60b29.camel@mediatek.com>
2023-12-18 9:33 ` Damien Le Moal
2023-12-19 7:16 ` Naohiro Aota
[not found] ` <dbc4a5b4296effd88ba0ef939aa324df0969545c.camel@mediatek.com>
2023-12-19 8:12 ` Damien Le Moal
2023-12-19 10:38 ` hch
2023-12-19 12:16 ` hch
2023-12-18 9:48 ` Damien Le Moal
2023-12-18 14:33 ` Christoph Hellwig
2023-12-17 16:53 ` [PATCH 4/5] block: simplify disk_set_zoned Christoph Hellwig
2023-12-18 9:50 ` Damien Le Moal
2023-12-17 16:53 ` [PATCH 5/5] sd: only call disk_clear_zoned when needed Christoph Hellwig
2023-12-18 9:51 ` Damien Le Moal
2023-12-19 2:16 ` remove support for the host aware zoned model Martin K. Petersen
2023-12-20 3:18 ` 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=20231218151330.GD12768@fedora \
--to=stefanha@redhat.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux.dev \
/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).