From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 0/3] Refactor blk_zone_wplug_handle_write()
Date: Wed, 12 Nov 2025 14:05:41 -0700 [thread overview]
Message-ID: <176298154147.89130.73445451656520455.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251111232903.953630-1-bvanassche@acm.org>
On Tue, 11 Nov 2025 15:28:59 -0800, Bart Van Assche wrote:
> 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,
>
> [...]
Applied, thanks!
[1/3] blk-zoned: Fix a typo in a source code comment
commit: fd0ae4754c7b2add72338b14ddc8c8ff5ffda426
[2/3] blk-zoned: Document disk_zone_wplug_schedule_bio_work() locking
commit: faa3be1a61bfaace4c2bd57434de7b13347f9f31
[3/3] blk-zoned: Move code from disk_zone_wplug_add_bio() into its caller
commit: f233339188cd9b1a985fd8410d5811e920fdd4ef
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-11-12 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 23:28 [PATCH v2 0/3] Refactor blk_zone_wplug_handle_write() Bart Van Assche
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 [this message]
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=176298154147.89130.73445451656520455.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--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