From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Cc: linux-kselftest@vger.kernel.org, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH V3 0/3] selftests: add ublk selftests
Date: Fri, 28 Feb 2025 09:38:19 -0700 [thread overview]
Message-ID: <174076069911.2584282.8980328813902207680.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250228161919.2869102-1-ming.lei@redhat.com>
On Sat, 01 Mar 2025 00:19:13 +0800, Ming Lei wrote:
> This patchset adds ublk kernel selftests, which is very handy for
> developer for verifying kernel change, especially ublk heavily depends
> on io_uring subsystem. Also it provides template for target implementation.
>
> Please consider it for v6.15.
>
> The 1st patch adds one ublk utility and one entry test.
> The 2nd patch adds test over file backed ublk.
> The 3rd patch adds test for ublk zero copy.
>
> [...]
Applied, thanks!
[1/3] selftests: ublk: add kernel selftests for ublk
commit: 6aecda00b7d1e187c31e702d607d2b51bbcddbcc
[2/3] selftests: ublk: add file backed ublk
commit: 5d95bfb5357111028b7a37464d1a18702722efe9
[3/3] selftests: ublk: add ublk zero copy test
commit: bedc9cbc5f9709b97646fe3423dbf530b74b09d5
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-02-28 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 16:19 [PATCH V3 0/3] selftests: add ublk selftests Ming Lei
2025-02-28 16:19 ` [PATCH V3 1/3] selftests: ublk: add kernel selftests for ublk Ming Lei
2025-02-28 16:19 ` [PATCH V3 2/3] selftests: ublk: add file backed ublk Ming Lei
2025-02-28 16:19 ` [PATCH V3 3/3] selftests: ublk: add ublk zero copy test Ming Lei
2025-02-28 16:37 ` [PATCH V3 0/3] selftests: add ublk selftests Jens Axboe
2025-03-01 1:11 ` Ming Lei
2025-03-01 2:19 ` Jens Axboe
2025-02-28 16:38 ` 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=174076069911.2584282.8980328813902207680.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ming.lei@redhat.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