From: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
tytso@mit.edu, 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: Sun, 16 Mar 2025 00:31:33 -0300 [thread overview]
Message-ID: <20250316033133.GA4963@eaf> (raw)
In-Reply-To: <20250314-apfs-v1-0-ddfaa6836b5c@ethancedwards.com>
Hi Ethan,
I'm happy to see your enthusiasm for my driver but, if you want to help, I
think you should simply send the changes you have in mind to the out-of-tree
repo. That way you'll start learning the codebase while I can review your
work and run xfstests for you. Filesystems are very dangerous things; I've
probably done a lot of damage myself back in the day trying to help out with
the hfs drivers.
As for upstreaming, the driver still has a few rough edges, but I don't
think that's the real reason I never tried to submit. I'm just no longer
confident that filesystem compatibility is a reasonable goal, and I don't
expect much interest from reviewers. There are too many risks, and too many
hardware restrictions these days; regular users have much easier (even if
slower) ways to move their files around. Other uses exist of course (like
Aditya can explain), but they are a bit esoteric. Of course if upstream
people disagree, and they do want the apfs support, I will be glad to
prepare a patch series.
Ernesto
next prev parent reply other threads:[~2025-03-16 3:31 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
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 [this message]
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=20250316033133.GA4963@eaf \
--to=ernesto.mnd.fernandez@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=ernesto@corellium.com \
--cc=ethan@ethancedwards.com \
--cc=gargaditya08@live.com \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.