[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <krww5lm4ot3qqgaxojipb5zyhrgtgjftvt4khdhcnsofmh2574@vyhzmrxf6vdk>
Date: Sat, 15 Mar 2025 10:13:34 -0400
From: Ethan Carter Edwards <ethan@...ancedwards.com>
To: Christian Brauner <brauner@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, tytso@....edu,
ernesto.mnd.fernandez@...il.com, dan.carpenter@...aro.org, sven@...npeter.dev,
ernesto@...ellium.com, gargaditya08@...e.com, willy@...radead.org,
asahi@...ts.linux.dev, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-staging@...ts.linux.dev
Subject: Re: [RFC PATCH 0/8] staging: apfs: init APFS module
On 25/03/15 10:18AM, Christian Brauner wrote:
> > But I'll wait for an ACK from the filesystem developers before doing it
> > as having filesystem code in drivers/staging/ feels odd, and they kind
> > of need to know what's going on here for when they change api stuff.
>
> Sorry, I don't want new filesystems going through the generic staging
> tree. Next week during LSFMM we can discuss a filesystem specific
> staging tree that is directly maintained as part of fs so it's tightly
> integrated. We're going to talk about two new filesystems anyway.
No problem! I understand. I just wanted to get the ball rolling and
start the conversation about this process. I am eager to hear back.
Thanks,
Ethan
>
> Thanks!
> Christian
Powered by blists - more mailing lists