From: Al Viro <viro@zeniv.linux.org.uk>
To: Jeff Layton <jlayton@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: remove locks_inode
Date: Wed, 11 Jan 2023 02:05:11 +0000 [thread overview]
Message-ID: <Y74ZVx8Vm1scSBMN@ZenIV> (raw)
In-Reply-To: <b38ad39f0572f31d27479f04bf085bd678887dc2.camel@kernel.org>
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@zeniv.linux.org.uk>
in case it's not obvious from the above...
next prev parent reply other threads:[~2023-01-11 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 10:44 [PATCH] fs: remove locks_inode Jeff Layton
2023-01-10 14:01 ` Miklos Szeredi
2023-01-10 23:59 ` Al Viro
2023-01-11 1:33 ` Jeff Layton
2023-01-11 2:05 ` Al Viro [this message]
2023-01-11 9:44 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y74ZVx8Vm1scSBMN@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=mszeredi@redhat.com \
--cc=trond.myklebust@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox