From: Alyssa Ross <hi@alyssa.is>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"axboe@kernel.dk" <axboe@kernel.dk>, "hch@lst.de" <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests] loop/009: add test for loop partition uvents
Date: Tue, 4 Apr 2023 18:45:34 +0000 [thread overview]
Message-ID: <20230404184534.t22goewekxb5yds6@x220> (raw)
In-Reply-To: <517f4449-ffef-f1e8-78cf-bae8c2cdf665@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Tue, Apr 04, 2023 at 06:29:00PM +0000, Chaitanya Kulkarni wrote:
> On 3/30/2023 9:02 AM, Alyssa Ross wrote:
> > Link: https://lore.kernel.org/r/20230320125430.55367-1-hch@lst.de/
> > Suggested-by: Chaitanya Kulkarni <chaitanyak@nvidia.com>
> > Signed-off-by: Alyssa Ross <hi@alyssa.is>
>
> Thanks a lot for this, overall this looks good to me.
>
> This does exactly the testing for loop configure that your patch
> is for, let's just make sure to apply this patch once your kernel
> patch is merged.
The kernel patch was included in v6.3-rc5. :)
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-04 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 12:54 [PATCH] loop: LOOP_CONFIGURE: send uevents for partitions Christoph Hellwig
2023-03-26 23:09 ` Chaitanya Kulkarni
2023-03-30 16:02 ` [PATCH blktests] loop/009: add test for loop partition uvents Alyssa Ross
2023-03-30 19:22 ` kernel test robot
2023-03-30 19:50 ` LKP kernel test robot and blktests patches Alyssa Ross
2023-03-31 15:26 ` Yujie Liu
2023-04-04 18:29 ` [PATCH blktests] loop/009: add test for loop partition uvents Chaitanya Kulkarni
2023-04-04 18:45 ` Alyssa Ross [this message]
2023-04-06 10:30 ` Shin'ichiro Kawasaki
2023-05-22 2:29 ` Shinichiro Kawasaki
2023-03-29 15:24 ` [PATCH] loop: LOOP_CONFIGURE: send uevents for partitions 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=20230404184534.t22goewekxb5yds6@x220 \
--to=hi@alyssa.is \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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