From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Cc: Uday Shankar <ushankar@purestorage.com>,
Caleb Sander Mateos <csander@purestorage.com>
Subject: Re: [PATCH 0/2] ublk: two fixes on UBLK_F_AUTO_BUF_REG
Date: Wed, 21 May 2025 14:31:27 -0600 [thread overview]
Message-ID: <b725e99c-d36f-484b-8281-284cde78334a@kernel.dk> (raw)
In-Reply-To: <174783310404.804195.9704387738908088189.b4-ty@kernel.dk>
On 5/21/25 7:11 AM, Jens Axboe wrote:
>
> On Wed, 21 May 2025 10:54:58 +0800, Ming Lei wrote:
>> The 1st patches fix ublk_fetch() failure path for setting auto-buf-reg
>> data.
>>
>> The 2nd patch makes sure that the buffer unregister is done in same
>> 'io_ring_ctx' for issuing FETCH command.
>>
>>
>> [...]
>
> Applied, thanks!
>
> [1/2] ublk: handle ublk_set_auto_buf_reg() failure correctly in ublk_fetch()
> commit: 5b2a1c40684ba59570b302a56de31defc8d514ee
> [2/2] ublk: run auto buf unregisgering in same io_ring_ctx with register
> commit: 349c41125d3945c53f2c3d48d7225dbdd2c99801
Dropped 2/2 for now.
--
Jens Axboe
prev parent reply other threads:[~2025-05-21 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 2:54 [PATCH 0/2] ublk: two fixes on UBLK_F_AUTO_BUF_REG Ming Lei
2025-05-21 2:54 ` [PATCH 1/2] ublk: handle ublk_set_auto_buf_reg() failure correctly in ublk_fetch() Ming Lei
2025-05-21 14:53 ` Caleb Sander Mateos
2025-05-21 2:55 ` [PATCH 2/2] ublk: run auto buf unregisgering in same io_ring_ctx with register Ming Lei
2025-05-21 15:58 ` Caleb Sander Mateos
2025-05-22 0:42 ` Ming Lei
2025-05-22 1:05 ` Caleb Sander Mateos
2025-05-22 2:37 ` Ming Lei
2025-05-21 19:19 ` Caleb Sander Mateos
2025-05-21 13:11 ` [PATCH 0/2] ublk: two fixes on UBLK_F_AUTO_BUF_REG Jens Axboe
2025-05-21 20:31 ` 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=b725e99c-d36f-484b-8281-284cde78334a@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=ushankar@purestorage.com \
/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