From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
"hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCH blktests 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme
Date: Tue, 3 Dec 2024 04:18:17 +0000 [thread overview]
Message-ID: <26ce9f0d-8104-44af-a648-46613e518ea7@nvidia.com> (raw)
In-Reply-To: <20241129080231.2994578-2-nilay@linux.ibm.com>
On 11/29/24 00:01, Nilay Shroff wrote:
> In a preparation for the use of nvmf_wait_for_ns function from
> other nvme test script, move nvmf_wait_for_ns from nvme/052 to
> common/nvme file so that we can reuse the nvmf_wait_for_ns from
> multiple test scripts.
>
> Signed-off-by: Nilay Shroff<nilay@linux.ibm.com>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-12-03 4:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 8:01 [PATCH blktests 0/2] add nvme test for creating sleep while atomic kernel BUG Nilay Shroff
2024-11-29 8:01 ` [PATCH blktests 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme Nilay Shroff
2024-12-03 4:18 ` Chaitanya Kulkarni [this message]
2024-11-29 8:01 ` [PATCH blktests 2/2] nvme: add test for writing to file-ns just after disabling it Nilay Shroff
2024-11-30 9:10 ` [PATCH blktests 0/2] add nvme test for creating sleep while atomic kernel BUG Shinichiro Kawasaki
2024-12-03 4:20 ` Chaitanya Kulkarni
2024-12-03 5:38 ` Nilay Shroff
2024-12-03 8:26 ` Shinichiro Kawasaki
2024-12-03 9:05 ` Nilay Shroff
2024-12-06 1:09 ` Shinichiro Kawasaki
2024-12-03 8:26 ` Chaitanya Kulkarni
2024-12-04 10:08 ` Nilay Shroff
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=26ce9f0d-8104-44af-a648-46613e518ea7@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
--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