From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH blktests] nvme/040: fix write file path
Date: Thu, 4 Aug 2022 06:47:12 +0000 [thread overview]
Message-ID: <d7371c19-5586-4182-9f7d-268aadd0024b@nvidia.com> (raw)
In-Reply-To: <20220729001505.1489933-1-shinichiro.kawasaki@wdc.com>
On 7/28/22 17:15, Shin'ichiro Kawasaki wrote:
> The test case nvme/040 performs I/O to a nvmf device file. However, it
> specifies wrong path to the device file then the I/O is done to a
> regular file. Hence fix the path.
>
> Fixes: ebf197d1aea4 ("nvme: add nvmf reset/disconnect during traffic test")
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> ---
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-08-04 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 0:15 [PATCH blktests] nvme/040: fix write file path Shin'ichiro Kawasaki
2022-08-04 6:47 ` Chaitanya Kulkarni [this message]
2022-08-04 7:54 ` 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=d7371c19-5586-4182-9f7d-268aadd0024b@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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