[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <custjjqmvxt2u3wfjztwjdxvdxr6vbpvcoptt4vvv2itt7d2os@zqg5es4g7xmf>
Date: Sat, 5 Jul 2025 14:27:45 -0500
From: John Groves <John@...ves.net>
To: Amir Goldstein <amir73il@...il.com>
Cc: Dan Williams <dan.j.williams@...el.com>,
Bernd Schubert <bschubert@....com>, John Groves <jgroves@...ron.com>,
Jonathan Corbet <corbet@....net>, Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>, Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
Alexander Viro <viro@...iv.linux.org.uk>, Christian Brauner <brauner@...nel.org>,
"Darrick J . Wong" <djwong@...nel.org>, Randy Dunlap <rdunlap@...radead.org>,
Jeff Layton <jlayton@...nel.org>, Kent Overstreet <kent.overstreet@...ux.dev>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-cxl@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Jonathan Cameron <Jonathan.Cameron@...wei.com>, Stefan Hajnoczi <shajnocz@...hat.com>,
Joanne Koong <joannelkoong@...il.com>, Josef Bacik <josef@...icpanda.com>,
Aravind Ramesh <arramesh@...ron.com>, Ajay Joshi <ajayjoshi@...ron.com>,
Miklos Szeredi <miklos@...redi.hu>
Subject: Re: [RFC V2 13/18] famfs_fuse: Create files with famfs fmaps
On 25/07/04 11:01AM, Amir Goldstein wrote:
> On Thu, Jul 3, 2025 at 8:51 PM John Groves <John@...ves.net> wrote:
> >
> > On completion of GET_FMAP message/response, setup the full famfs
> > metadata such that it's possible to handle read/write/mmap directly to
> > dax. Note that the devdax_iomap plumbing is not in yet...
> >
> > Update MAINTAINERS for the new files.
> >
> > Signed-off-by: John Groves <john@...ves.net>
> > ---
> > MAINTAINERS | 9 +
> > fs/fuse/Makefile | 2 +-
> > fs/fuse/famfs.c | 360 ++++++++++++++++++++++++++++++++++++++
> > fs/fuse/famfs_kfmap.h | 63 +++++++
> > fs/fuse/file.c | 15 +-
> > fs/fuse/fuse_i.h | 16 +-
> > fs/fuse/inode.c | 2 +-
> > include/uapi/linux/fuse.h | 56 ++++++
> > 8 files changed, 518 insertions(+), 5 deletions(-)
> > create mode 100644 fs/fuse/famfs.c
> > create mode 100644 fs/fuse/famfs_kfmap.h
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index c0d5232a473b..02688f27a4d0 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -8808,6 +8808,15 @@ F: Documentation/networking/failover.rst
> > F: include/net/failover.h
> > F: net/core/failover.c
> >
> > +FAMFS
> > +M: John Groves <jgroves@...ron.com>
> > +M: John Groves <John@...ves.net>
> > +L: linux-cxl@...r.kernel.org
> > +L: linux-fsdevel@...r.kernel.org
> > +S: Supported
> > +F: fs/fuse/famfs.c
> > +F: fs/fuse/famfs_kfmap.h
> > +
>
> I suggest to follow the pattern of MAINTAINERS sub entries
> FILESYSTEMS [EXPORTFS]
> FILESYSTEMS [IOMAP]
>
> and call this sub entry
> FUSE [FAMFS]
>
> to order it following FUSE entry
>
> Thanks,
> Amir.
Done, and queued to -next
Thanks,
John
Powered by blists - more mailing lists