On 25/07/04 11:01AM, Amir Goldstein wrote: > On Thu, Jul 3, 2025 at 8:51 PM John Groves <John@xxxxxxxxxx> 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@xxxxxxxxxx> > > --- > > 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@xxxxxxxxxx> > > +M: John Groves <John@xxxxxxxxxx> > > +L: linux-cxl@xxxxxxxxxxxxxxx > > +L: linux-fsdevel@xxxxxxxxxxxxxxx > > +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
