From: Guixin Liu <kanie@linux.alibaba.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "dwagner@suse.de" <dwagner@suse.de>,
"chaitanyak@nvidia.com" <chaitanyak@nvidia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH blktests v3] nvme/{common/nvme, 016, 017, 051, 052}: introduce def_nsid
Date: Wed, 6 Nov 2024 09:42:23 +0800 [thread overview]
Message-ID: <e5125a46-4fcc-450c-99a7-5a807989cf98@linux.alibaba.com> (raw)
In-Reply-To: <uidk3q376j4rahmw5wnpnoycd7pb4nvgzr723okznlx3pkejln@hssxf773zv4q>
在 2024/11/5 18:30, Shinichiro Kawasaki 写道:
> On Oct 31, 2024 / 18:14, Guixin Liu wrote:
>> Use def_nsid instead of hard code, the default of def_nsid is 1.
>>
>> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
>> Reviewed-by: Daniel Wagner <dwagner@suse.de>
>> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
>> ---
>> Changes from v2 to v3:
>> - Fix 016, 017, 052 do nothing when the def_nsid is set to
>> biger than iterations.(Shinichiro Kawasaki)
>> - Fix "make check" error in 052.(Shinichiro Kawasaki)
> Guixin, thank you for this v3. I've applied the patch.
>
> Unfortunately, this patch caused some conflicts with the series "nvme: prepare
> for ANA support", so I took the liberty to modify this change. Please take a
> look in the commit after the modification [1]. If there is any mistakes, please
> let me know.
>
> [1] https://github.com/osandov/blktests/commit/87d4c0cb93f32b7d0798b9faaed6bb2b39d636a2
Looks like I'm missing to add "local nsid", thanks for modifing this.
Best Regards,
Guixin Liu
prev parent reply other threads:[~2024-11-06 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 10:14 [PATCH blktests v3] nvme/{common/nvme, 016, 017, 051, 052}: introduce def_nsid Guixin Liu
2024-11-05 10:30 ` Shinichiro Kawasaki
2024-11-06 1:42 ` Guixin Liu [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=e5125a46-4fcc-450c-99a7-5a807989cf98@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=linux-nvme@lists.infradead.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