[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b38ad39f0572f31d27479f04bf085bd678887dc2.camel@kernel.org>
Date: Tue, 10 Jan 2023 20:33:45 -0500
From: Jeff Layton <jlayton@...nel.org>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: David Howells <dhowells@...hat.com>,
Marc Dionne <marc.dionne@...istor.com>,
Trond Myklebust <trond.myklebust@...merspace.com>,
Anna Schumaker <anna@...nel.org>,
Chuck Lever <chuck.lever@...cle.com>,
Miklos Szeredi <mszeredi@...hat.com>,
linux-afs@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-nfs@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] fs: remove locks_inode
On Tue, 2023-01-10 at 23:59 +0000, Al Viro wrote:
> On Tue, Jan 10, 2023 at 05:44:59AM -0500, Jeff Layton wrote:
> > locks_inode was turned into a wrapper around file_inode in de2a4a501e71
> > (Partially revert "locks: fix file locking on overlayfs"). Finish
> > replacing locks_inode invocations everywhere with file_inode.
>
> Looks good to me. Which tree do you want that to go through?
I'll take it via the file locking tree, if that's ok. Let me know if
you'd rather pick it up though.
--
Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists