[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <glfjkah5e54ymq75lp46akttuqrsccigb445nchcpe4ahixzxk@5al3wjxify5d>
Date: Thu, 17 Aug 2023 02:55:25 +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>,
Max Gurtovoy <mgurtovoy@...dia.com>,
Hannes Reinecke <hare@...e.de>,
Sagi Grimberg <sagi@...mberg.me>,
James Smart <jsmart2021@...il.com>,
Bart Van Assche <bvanassche@....org>
Subject: Re: [PATCH blktests v2 00/12] Switch to allowed_host
On Aug 11, 2023 / 09:00, Daniel Wagner wrote:
[...]
> BTW, what do you think about removing nvme/006 and nvme/007? They are
> basically doing nothing anymore except setting up a target with either
> device or file backing. We exercise this code now in all the other
> tests. So this is bit redundant IMO.
I think the test cases are meaningful. They confirm that target set up feature
is working good. When other test cases fail, we can refer nvme/006 and nvme/007
results and see if the failure cause is in target set up or not.
Powered by blists - more mailing lists