[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <537092.1589626426@warthog.procyon.org.uk>
Date: Sat, 16 May 2020 11:53:46 +0100
From: David Howells <dhowells@...hat.com>
To: Trond Myklebust <trondmy@...merspace.com>
Cc: dhowells@...hat.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"viro@...IV.linux.org.uk" <viro@...IV.linux.org.uk>,
"anna.schumaker@...app.com" <anna.schumaker@...app.com>
Subject: Re: [PATCH -next] nfs: fsinfo: fix build when CONFIG_NFS_V4 is not enabled
Trond Myklebust <trondmy@...merspace.com> wrote:
> This whole thing needs to be reviewed and acked by the NFS community,
> and quite frankly I'm inclined to NAK this. This is the second time
> David tries to push this unwanted rewrite of totally unrelated code.
Rewrite? What?
It's example code of what NFS could export through this interface. I didn't
submit it to Linus with the rest of the patches as it's only an example; same
for the ext4 example. I've tried running it past you and other NFS people a
couple of times to try and elicit a response and wanted to try and ask you
about it at LSF:-(
Anyway, I've dropped it for now.
David
Powered by blists - more mailing lists