[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1923896038.379134.1612901174023.JavaMail.zimbra@nod.at>
Date: Tue, 9 Feb 2021 21:06:14 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Vignesh Raghavendra <vigneshr@...com>,
Boris Brezillon <boris.brezillon@...labora.com>,
Ron Minnich <rminnich@...gle.com>, sven <sven@...fation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
fuse-devel <fuse-devel@...ts.sourceforge.net>
Subject: Re: [PATCH 0/8] MUSE: Userspace backed MTD v3
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
Powered by blists - more mailing lists