From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Ethan Carter Edwards <ethan@ethancedwards.com>,
tytso@mit.edu, ernesto.mnd.fernandez@gmail.com,
dan.carpenter@linaro.org, sven@svenpeter.dev,
ernesto@corellium.com, gargaditya08@live.com,
willy@infradead.org, asahi@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [RFC PATCH 0/8] staging: apfs: init APFS module
Date: Sat, 15 Mar 2025 10:32:08 +0100 [thread overview]
Message-ID: <2025031554-agreeing-ammonium-58aa@gregkh> (raw)
In-Reply-To: <20250315-gruft-evidenz-d2054ba2f684@brauner>
On Sat, Mar 15, 2025 at 10:18:23AM +0100, 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.
Great, then I'll not worry about this patch series at all, thanks!
greg k-h
next prev parent reply other threads:[~2025-03-15 9:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 21:57 [RFC PATCH 0/8] staging: apfs: init APFS module Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 1/8] staging: apfs: init lzfse compression library for APFS Ethan Carter Edwards
2025-03-15 7:12 ` Aditya Garg
2025-03-15 14:08 ` Ethan Carter Edwards
2025-03-15 9:41 ` Dan Carpenter
2025-03-15 14:14 ` Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 2/8] staging: apfs: init unicode.{c,h} Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 3/8] staging: apfs: init apfs_raw.h to handle on-disk structures Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 4/8] staging: apfs: init libzbitmap.{c,h} for decompression Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 5/8] staging: apfs: init APFS Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 6/8] staging: apfs: init build support for APFS Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 7/8] staging: apfs: init TODO and README.rst Ethan Carter Edwards
2025-03-14 21:57 ` [PATCH RFC 8/8] MAINTAINERS: apfs: add entry and relevant information Ethan Carter Edwards
2025-03-15 7:00 ` [RFC PATCH 0/8] staging: apfs: init APFS module Greg Kroah-Hartman
2025-03-15 9:18 ` Christian Brauner
2025-03-15 9:32 ` Greg Kroah-Hartman [this message]
2025-03-15 14:13 ` Ethan Carter Edwards
2025-03-15 14:04 ` Ethan Carter Edwards
2025-03-15 7:10 ` Aditya Garg
2025-03-15 7:21 ` Aditya Garg
2025-03-15 14:12 ` Ethan Carter Edwards
2025-03-15 14:34 ` Aditya Garg
2025-03-15 14:35 ` Aditya Garg
2025-03-15 14:06 ` Ethan Carter Edwards
2025-03-16 3:31 ` Ernesto A. Fernández
2025-03-16 6:31 ` Aditya Garg
2025-03-16 15:48 ` Ethan Carter Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025031554-agreeing-ammonium-58aa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=asahi@lists.linux.dev \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=ernesto.mnd.fernandez@gmail.com \
--cc=ernesto@corellium.com \
--cc=ethan@ethancedwards.com \
--cc=gargaditya08@live.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sven@svenpeter.dev \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox