Miklos, ----- Ursprüngliche Mail ----- >> I do wonder if MUSE should go to drivers/mtd/ instead. Long term >> goal would be move CUSE to drivers/char and move the transport part of >> fuse into net/fuse leaving only the actual filesystems (fuse and >> virtiofs) under fs/. >> >> But for now just moving the minimal interface needed for MUSE into a >> separate header (<net/fuse.h>) would work, I guess. >> >> Do you think that would make sense? > > Yes, I'm all for having MUSE in drivers/mtd/. > > I placed MUSE initially in fs/fuse/ because CUSE was already there and muse.c > includes > fuse_i.h. So tried to be as little invasive as possible.
I did a quick patch series which moves CUSE into drivers/char/ https://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git/log/?h=fs_fuse_split Does this more or less what you had in mind? If so, I'd submit these patches, rebase MUSE on them and do a v4 soon. Thanks, //richard
