From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH v2 2/5] block: split blk_zone_update_request_bio into two functions
Date: Tue, 15 Jul 2025 07:33:02 +0200 [thread overview]
Message-ID: <20250715053302.GA18074@lst.de> (raw)
In-Reply-To: <20250714143825.3575-3-johannes.thumshirn@wdc.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-07-15 5:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 14:38 [PATCH v2 0/5] block: add tracepoints for ZBD specific operations Johannes Thumshirn
2025-07-14 14:38 ` [PATCH v2 1/5] blktrace: add zoned block commands to blk_fill_rwbs Johannes Thumshirn
2025-07-14 16:32 ` Bart Van Assche
2025-07-14 21:32 ` Bart Van Assche
2025-07-14 22:34 ` Chaitanya Kulkarni
2025-07-14 14:38 ` [PATCH v2 2/5] block: split blk_zone_update_request_bio into two functions Johannes Thumshirn
2025-07-14 16:34 ` Bart Van Assche
2025-07-14 22:36 ` Chaitanya Kulkarni
2025-07-15 5:33 ` Christoph Hellwig [this message]
2025-07-14 14:38 ` [PATCH v2 3/5] block: add tracepoint for blk_zone_update_request_bio Johannes Thumshirn
2025-07-14 16:35 ` Bart Van Assche
2025-07-14 22:36 ` Chaitanya Kulkarni
2025-07-15 5:33 ` Christoph Hellwig
2025-07-14 14:38 ` [PATCH v2 4/5] block: add tracepoint for blkdev_zone_mgmt Johannes Thumshirn
2025-07-14 16:35 ` Bart Van Assche
2025-07-14 22:37 ` Chaitanya Kulkarni
2025-07-15 5:33 ` Christoph Hellwig
2025-07-14 14:38 ` [PATCH v2 5/5] block: add trace messages to zone write plugging Johannes Thumshirn
2025-07-14 16:43 ` Bart Van Assche
2025-07-15 5:39 ` Johannes Thumshirn
2025-07-14 17:48 ` Bart Van Assche
2025-07-14 22:38 ` Chaitanya Kulkarni
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=20250715053302.GA18074@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--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.