[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y74ZVx8Vm1scSBMN@ZenIV>
Date: Wed, 11 Jan 2023 02:05:11 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Jeff Layton <jlayton@...nel.org>
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, Jan 10, 2023 at 08:33:45PM -0500, Jeff Layton wrote:
> 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.
Fine by me - I don't have anything pending in that area, so... Oh, and
ACKed-by: Al Viro <viro@...iv.linux.org.uk>
in case it's not obvious from the above...
Powered by blists - more mailing lists