From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/3] Refactor blk_zone_wplug_handle_write()
Date: Tue, 11 Nov 2025 15:28:59 -0800 [thread overview]
Message-ID: <20251111232903.953630-1-bvanassche@acm.org> (raw)
Hi Jens,
This series includes three small patches for the zoned block device code: a
typo is fixed, a lockdep annotation is added and the code for handling zoned
writes is made slightly easier to follow. Please consider these patches for the
next merge window.
Thanks,
Bart.
Changes compared to v1:
- Combined patches 3 and 4 into a single patch.
- Renamed a goto label.
- Removed the local variable "schedule_bio_work".
Bart Van Assche (3):
blk-zoned: Fix a typo in a source code comment
blk-zoned: Document disk_zone_wplug_schedule_bio_work() locking
blk-zoned: Move code from disk_zone_wplug_add_bio() into its caller
block/blk-zoned.c | 46 ++++++++++++++++++++--------------------------
1 file changed, 20 insertions(+), 26 deletions(-)
next reply other threads:[~2025-11-11 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 23:28 Bart Van Assche [this message]
2025-11-11 23:29 ` [PATCH v2 1/3] blk-zoned: Fix a typo in a source code comment Bart Van Assche
2025-11-11 23:29 ` [PATCH v2 2/3] blk-zoned: Document disk_zone_wplug_schedule_bio_work() locking Bart Van Assche
2025-11-11 23:29 ` [PATCH v2 3/3] blk-zoned: Move code from disk_zone_wplug_add_bio() into its caller Bart Van Assche
2025-11-12 8:31 ` Christoph Hellwig
2025-11-12 8:36 ` Damien Le Moal
2025-11-12 21:04 ` [PATCH v2 0/3] Refactor blk_zone_wplug_handle_write() Martin K. Petersen
2025-11-12 21:05 ` 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=20251111232903.953630-1-bvanassche@acm.org \
--to=bvanassche@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox