[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240220133158.GL40273@kernel.org>
Date: Tue, 20 Feb 2024 13:31:58 +0000
From: Simon Horman <horms@...nel.org>
To: David Howells <dhowells@...hat.com>
Cc: Steve French <smfrench@...il.com>, Jeff Layton <jlayton@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
Paulo Alcantara <pc@...guebit.com>,
Shyam Prasad N <sprasad@...rosoft.com>, Tom Talpey <tom@...pey.com>,
Christian Brauner <christian@...uner.io>, netfs@...ts.linux.dev,
linux-cifs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Steve French <sfrench@...ba.org>,
Shyam Prasad N <nspmangalore@...il.com>,
Rohith Surabattula <rohiths.msft@...il.com>
Subject: Re: [PATCH v5 09/12] cifs: Cut over to using netfslib
On Mon, Feb 19, 2024 at 03:10:44PM +0000, David Howells wrote:
> Simon Horman <horms@...nel.org> wrote:
>
> > > /* Functions related to files and directories */
> > > +extern const struct netfs_request_ops cifs_req_ops;
> > > extern const struct file_operations cifs_file_ops;
> > > extern const struct file_operations cifs_file_direct_ops; /* if directio mnt */
> > > extern const struct file_operations cifs_file_strict_ops; /* if strictio mnt */
> >
> > Nit: this hunk would probably be better placed in the
> > patch at adds cifs_req_ops to fs/smb/client/file.c
>
> I'm not sure I understand what you mean. Is there a bit missing between "at"
> and "adds" in that?
Sorry, "patch that adds".
What I meant is, the declaration of cifs_req_ops and it's definition
seem to appear in different patches of this series. And it might
make sense if they were both in the same patch. But given that
both are present by the end of the series it is more cosmetic
than anything else.
Powered by blists - more mailing lists