From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests v3 0/2] blktests: add mini ublk source and blktests/033
Date: Mon, 20 Feb 2023 13:03:13 +0000 [thread overview]
Message-ID: <20230220130311.ilddmkvojgobvgpe@shindev> (raw)
In-Reply-To: <20230220034649.1522978-1-ming.lei@redhat.com>
On Feb 20, 2023 / 11:46, Ming Lei wrote:
> Hello,
>
> The 1st patch adds one mini ublk program, which only supports null &
> loop targets.
>
> The 2nd patch add blktests/033 for covering gendisk leak issue.
>
> v3:
> - move minublk.c into src/
> - remove '-i' in top Makefile
> - fix commit log for 1/2
> - add 'udevadm settle' after adding device, so that the following
> test can be done reliably
> - fix _init_ublk()
> - redirect runtime log into $FULL
> - all are suggested by Shinichiro Kawasaki
Ming, thanks for v3. The patches look good to me. I'll wait for a few more days
before merge in case someone have more comments.
--
Shin'ichiro Kawasaki
prev parent reply other threads:[~2023-02-20 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 3:46 [PATCH blktests v3 0/2] blktests: add mini ublk source and blktests/033 Ming Lei
2023-02-20 3:46 ` [PATCH blktests v3 1/2] src: add mini ublk source code Ming Lei
2023-02-21 19:58 ` Chaitanya Kulkarni
2023-02-24 8:40 ` Ming Lei
2023-02-24 8:45 ` Ming Lei
2023-02-24 7:52 ` Ziyang Zhang
2023-02-24 8:28 ` Ming Lei
2023-02-24 11:41 ` Shinichiro Kawasaki
2023-02-27 2:57 ` Ziyang Zhang
2023-02-27 5:41 ` Shinichiro Kawasaki
2023-02-27 6:10 ` Ziyang Zhang
2023-02-28 9:25 ` Shinichiro Kawasaki
2023-02-20 3:46 ` [PATCH blktests v3 2/2] block/033: add test to cover gendisk leak Ming Lei
2023-02-20 13:03 ` Shinichiro Kawasaki [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=20230220130311.ilddmkvojgobvgpe@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=linux-block@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