[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4zt5oysmqw72l4xzfja2oer72hryisz6zzbboz7dmhhzfypuwx@yrf2utjkv66b>
Date: Sun, 7 May 2023 23:34:51 +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>,
Shin'ichiro Kawasaki <shinichiro@...tmail.com>,
Hannes Reinecke <hare@...e.de>
Subject: Re: [PATCH blktests v3 11/12] nvme/rc: Move discovery generation
counter code to rc
On May 03, 2023 / 10:02, Daniel Wagner wrote:
> Move the discovery generation counter code to rc so that we can reuse
> it in 002.
The last #12 patch no longer touches nvme/002, then I'm not so sure this patch
is valuable. IMO, the lengthy 002.out has the role to check all of the 1000
times discoveries are successful. So it looks the better to keep current
nvme/002 as is.
Powered by blists - more mailing lists