Messages in this thread | | | Subject | Re: [PATCH v2] filelock: move file locking definitions to separate header file | From | Jeff Layton <> | Date | Wed, 11 Jan 2023 05:09:22 -0500 |
| |
On Wed, 2023-01-11 at 02:12 +0000, Al Viro wrote: > On Thu, Jan 05, 2023 at 04:19:29PM -0500, Jeff Layton wrote: > > The file locking definitions have lived in fs.h since the dawn of time, > > but they are only used by a small subset of the source files that > > include it. > > > > Move the file locking definitions to a new header file, and add the > > appropriate #include directives to the source files that need them. By > > doing this we trim down fs.h a bit and limit the amount of rebuilding > > that has to be done when we make changes to the file locking APIs. > > > > Reviewed-by: Xiubo Li <xiubli@redhat.com> > > Reviewed-by: Christian Brauner (Microsoft) <brauner@kernel.org> > > Reviewed-by: Christoph Hellwig <hch@lst.de> > > Reviewed-by: David Howells <dhowells@redhat.com> > > Acked-by: Chuck Lever <chuck.lever@oracle.com> > > Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com> > > Acked-by: Steve French <stfrench@microsoft.com> > > Signed-off-by: Jeff Layton <jlayton@kernel.org> > > Same question re git tree preferences (and my Acked-by in any case)
I'll take this one via the file locking tree as well. FWIW, I have some other filelock API changes I'd like to propose, so I think that'll be easier.
Thanks, -- Jeff Layton <jlayton@kernel.org>
| |