[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y7375Zo5pE7g4P4H@ZenIV>
Date: Tue, 10 Jan 2023 23:59:33 +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 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?
Powered by blists - more mailing lists