[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <738326.1631645944@warthog.procyon.org.uk>
Date: Tue, 14 Sep 2021 19:59:04 +0100
From: David Howells <dhowells@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: dhowells@...hat.com, Trond Myklebust <trondmy@...merspace.com>,
Anna Schumaker <anna.schumaker@...app.com>,
Steve French <sfrench@...ba.org>,
Dominique Martinet <asmadeus@...ewreck.org>,
"open list:NFS, SUNRPC, AND..." <linux-nfs@...r.kernel.org>,
v9fs-developer@...ts.sourceforge.net,
Trond Myklebust <trond.myklebust@...merspace.com>,
linux-cachefs@...hat.com, CIFS <linux-cifs@...r.kernel.org>,
Shyam Prasad N <nspmangalore@...il.com>,
Jeff Layton <jlayton@...hat.com>,
Matthew Wilcox <willy@...radead.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-afs@...ts.infradead.org, ceph-devel@...r.kernel.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/8] fscache: Replace and remove old I/O API
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> > Call it "fallback" or "simple" or something that shows the intent, but
> > no, I'm not taking patches that introduce a _new_ interface and call
> > it "deprecated".
Yeah, I'll change it to "fallback" - I started talking about it like that in
the docs anyway.
> Put another way: to call something "deprecated", you have to already
> have the replacement all ready to go.
We're not far off. There's a fair distance (in number of patches) between
this patchset and the completion, hence why I marked them as deprecated here,
intending to remove them at the end. Between myself, Jeff and Dave we have
fscache, cachefiles, afs, ceph and nfs (almost) covered. I have patches for
9p and I've given a partial patch for cifs to Steve and Shyam.
David
Powered by blists - more mailing lists