From: Daniel Wagner <dwagner@suse.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-nvme@lists.infradead.org, shinichiro.kawasaki@wdc.com,
chaitanyak@nvidia.com, hch@lst.de, kbusch@kernel.org,
sagi@grimberg.me, axboe@kernel.dk, gjoyce@linux.ibm.com
Subject: Re: [PATCHv3 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme
Date: Fri, 6 Dec 2024 13:27:35 +0100 [thread overview]
Message-ID: <f8bacd12-8ed4-45d9-9d70-eecb0b6964ae@flourine.local> (raw)
In-Reply-To: <20241206111812.489140-2-nilay@linux.ibm.com>
On Fri, Dec 06, 2024 at 04:48:07PM +0530, 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.
>
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
Reviewed-by: Daniel Wagner <dwagner@suse.de>
next prev parent reply other threads:[~2024-12-06 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 11:18 [PATCHv3 0/2] add nvme test for creating sleep while atomic kernel BUG Nilay Shroff
2024-12-06 11:18 ` [PATCHv3 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme Nilay Shroff
2024-12-06 12:27 ` Daniel Wagner [this message]
2024-12-24 11:29 ` Sagi Grimberg
2024-12-06 11:18 ` [PATCHv3 2/2] nvme: add test for writing to file-ns just after disabling it Nilay Shroff
2024-12-06 12:32 ` Daniel Wagner
2024-12-06 12:50 ` Nilay Shroff
2024-12-24 11:29 ` Sagi Grimberg
2024-12-09 7:16 ` [PATCHv3 0/2] add nvme test for creating sleep while atomic kernel BUG Chaitanya Kulkarni
2024-12-09 11:50 ` Shinichiro Kawasaki
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=f8bacd12-8ed4-45d9-9d70-eecb0b6964ae@flourine.local \
--to=dwagner@suse.de \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--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