[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190221153415.GL11489@garbanzo.do-not-panic.com>
Date: Thu, 21 Feb 2019 07:34:15 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: "Theodore Y. Ts'o" <tytso@....edu>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Sasha Levin <sashal@...nel.org>,
Greg KH <gregkh@...uxfoundation.org>,
Amir Goldstein <amir73il@...il.com>,
Steve French <smfrench@...il.com>,
lsf-pc@...ts.linux-foundation.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [LSF/MM TOPIC] FS, MM, and stable trees
On Sat, Feb 16, 2019 at 01:28:35PM -0500, Theodore Y. Ts'o wrote:
> The block/*, loop/* and scsi/* tests in blktests do seem to be in
> pretty good shape. The nvme, nvmeof, and srp tests are *definitely*
> not as mature.
Can you say more about this later part. What would you like to see more
of for nvme tests for instance?
It sounds like a productive session would include tracking our:
a) sour spots
b) who's already working on these
c) gather volutneers for these sour spots
Luis
Powered by blists - more mailing lists