[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <455c7sf4hrgppludozegzjzkkdrqjujvguzgqwsjiz6bnsbmva@g7h6bkzdlada>
Date: Mon, 28 Aug 2023 04:17:14 +0000
From: Shinichiro Kawasaki <shinichiro.kawasaki@....com>
To: Daniel Wagner <dwagner@...e.de>
CC: "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
Chaitanya Kulkarni <kch@...dia.com>,
Hannes Reinecke <hare@...e.de>,
Sagi Grimberg <sagi@...mberg.me>,
Jason Gunthorpe <jgg@...pe.ca>
Subject: Re: [PATCH blktests v3 3/3] nvme: introduce
nvmet_target_{setup/cleanup} common code
On Aug 22, 2023 / 10:38, Daniel Wagner wrote:
[...]
> diff --git a/tests/nvme/015 b/tests/nvme/015
> index bc04e39c628c..b418d785ab27 100755
> --- a/tests/nvme/015
> +++ b/tests/nvme/015
> @@ -20,19 +20,12 @@ test() {
>
> _setup_nvmet
>
> - local port
> local nvmedev
> local size
> local bs
> local count
>
> - truncate -s "${nvme_img_size}" "${def_file_path}"
> -
> - _create_nvmet_subsystem "${def_subsysnqn}" "${def_file_path}" \
> - "${def_subsys_uuid}"
> - port="$(_create_nvmet_port "${nvme_trtype}")"
> - _add_nvmet_subsys_to_port "${port}" "${def_subsysnqn}"
> - _create_nvmet_host "${def_subsysnqn}" "${def_hostnqn}"
> + _nvmet_target_setup --blkdev=file
I looked back and found that the option above looks wrong. I think it should be
"--blkdev file" instead of "--blkedev=file".
Same for other _nvmet_target_setup calls with the option.
Powered by blists - more mailing lists