From: Aditya Garg <gargaditya08@live.com>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"tytso@mit.edu" <tytso@mit.edu>,
"ernesto.mnd.fernandez@gmail.com"
<ernesto.mnd.fernandez@gmail.com>,
"dan.carpenter@linaro.org" <dan.carpenter@linaro.org>,
"sven@svenpeter.dev" <sven@svenpeter.dev>,
"ernesto@corellium.com" <ernesto@corellium.com>,
"willy@infradead.org" <willy@infradead.org>,
"asahi@lists.linux.dev" <asahi@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>
Subject: Re: [RFC PATCH 0/8] staging: apfs: init APFS module
Date: Sat, 15 Mar 2025 07:21:07 +0000 [thread overview]
Message-ID: <D4E1167D-9AF8-4B1D-90FB-20F7507B595C@live.com> (raw)
In-Reply-To: <881481D8-AB70-4286-A5FB-731E5C957137@live.com>
> On 15 Mar 2025, at 12:39 PM, Aditya Garg <gargaditya08@live.com> wrote:
>
>
>
>> On 15 Mar 2025, at 3:27 AM, Ethan Carter Edwards <ethan@ethancedwards.com> wrote:
>>
>> Hello everyone,
>>
>> This is a follow up patchset to the driver I sent an email about a few
>> weeks ago [0]. I understand this patchset will probably get rejected,
>> but I wanted to report on what I have done thus far. I have got the
>> upstream module imported and building, and it passes some basic tests
>> so far (I have not tried getting XFS/FStests running yet).
>>
>> Like mentioned earlier, some of the files have been moved to folios, but
>> a large majority of them still use bufferheads. I would like to have
>> them completely removed before moved from staging/ into fs/.
>>
>> I have split everything up into separate commits as best as I could.
>> Most of the C files rely in functions from other C files, so I included
>> them all in one patch/commit.
>>
>> I am curious to hear everyone's thoughts on this and to start getting
>> the ball rolling for the code-review process. Please feel free to
>> include/CC anyone who may be interested in this driver/the review
>> process. I have included a few people, but have certainly missed others.
>>
>> [0]: https://lore.kernel.org/lkml/20250307165054.GA9774@eaf/
>>
>> Signed-off-by: Ethan Carter Edwards <ethan@ethancedwards.com>
>
> Why hasn’t Ernesto signed-off here, or in any patch? AFAIK, he is the author of the driver.
I can also see your Copyright at some places, which I didn't find in the upstream repo. Did you add some code change?
IMO, if you are just maintaining it, doesn't mean you add your copyright. Eg: I maintain the appletbdrm driver, but I didn't write or add anything special in it, so it doesn’t have my copyright.
Also, did you ask Ernesto whether he wants to be a co maintainer?
>> ---
>> Ethan Carter Edwards (8):
>> staging: apfs: init lzfse compression library for APFS
>> staging: apfs: init unicode.{c,h}
>> staging: apfs: init apfs_raw.h to handle on-disk structures
>> staging: apfs: init libzbitmap.{c,h} for decompression
>> staging: apfs: init APFS
>> staging: apfs: init build support for APFS
>> staging: apfs: init TODO and README.rst
>> MAINTAINERS: apfs: add entry and relevant information
>>
>> MAINTAINERS | 6 +
>> drivers/staging/Kconfig | 2 +
>> drivers/staging/apfs/Kconfig | 13 +
>> drivers/staging/apfs/Makefile | 10 +
>> drivers/staging/apfs/README.rst | 87 +
>> drivers/staging/apfs/TODO | 7 +
>> drivers/staging/apfs/apfs.h | 1193 ++++++++
>> drivers/staging/apfs/apfs_raw.h | 1567 +++++++++++
>> drivers/staging/apfs/btree.c | 1174 ++++++++
>> drivers/staging/apfs/compress.c | 442 +++
>> drivers/staging/apfs/dir.c | 1440 ++++++++++
>> drivers/staging/apfs/extents.c | 2371 ++++++++++++++++
>> drivers/staging/apfs/file.c | 164 ++
>> drivers/staging/apfs/inode.c | 2235 +++++++++++++++
>> drivers/staging/apfs/key.c | 337 +++
>> drivers/staging/apfs/libzbitmap.c | 442 +++
>> drivers/staging/apfs/libzbitmap.h | 31 +
>> drivers/staging/apfs/lzfse/lzfse.h | 136 +
>> drivers/staging/apfs/lzfse/lzfse_decode.c | 74 +
>> drivers/staging/apfs/lzfse/lzfse_decode_base.c | 652 +++++
>> drivers/staging/apfs/lzfse/lzfse_encode.c | 163 ++
>> drivers/staging/apfs/lzfse/lzfse_encode_base.c | 826 ++++++
>> drivers/staging/apfs/lzfse/lzfse_encode_tables.h | 218 ++
>> drivers/staging/apfs/lzfse/lzfse_fse.c | 217 ++
>> drivers/staging/apfs/lzfse/lzfse_fse.h | 606 +++++
>> drivers/staging/apfs/lzfse/lzfse_internal.h | 612 +++++
>> drivers/staging/apfs/lzfse/lzfse_main.c | 336 +++
>> drivers/staging/apfs/lzfse/lzfse_tunables.h | 60 +
>> drivers/staging/apfs/lzfse/lzvn_decode_base.c | 721 +++++
>> drivers/staging/apfs/lzfse/lzvn_decode_base.h | 68 +
>> drivers/staging/apfs/lzfse/lzvn_encode_base.c | 593 ++++
>> drivers/staging/apfs/lzfse/lzvn_encode_base.h | 116 +
>> drivers/staging/apfs/message.c | 29 +
>> drivers/staging/apfs/namei.c | 133 +
>> drivers/staging/apfs/node.c | 2069 ++++++++++++++
>> drivers/staging/apfs/object.c | 315 +++
>> drivers/staging/apfs/snapshot.c | 684 +++++
>> drivers/staging/apfs/spaceman.c | 1433 ++++++++++
>> drivers/staging/apfs/super.c | 2099 ++++++++++++++
>> drivers/staging/apfs/symlink.c | 78 +
>> drivers/staging/apfs/transaction.c | 959 +++++++
>> drivers/staging/apfs/unicode.c | 3156 ++++++++++++++++++++++
>> drivers/staging/apfs/unicode.h | 27 +
>> drivers/staging/apfs/xattr.c | 912 +++++++
>> drivers/staging/apfs/xfield.c | 171 ++
>> 45 files changed, 28984 insertions(+)
>> ---
>> base-commit: 695caca9345a160ecd9645abab8e70cfe849e9ff
>> change-id: 20250210-apfs-9d4478785f80
>>
>> Best regards,
>> --
>> Ethan Carter Edwards <ethan@ethancedwards.com>
next prev parent reply other threads:[~2025-03-15 7:21 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 [this message]
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=D4E1167D-9AF8-4B1D-90FB-20F7507B595C@live.com \
--to=gargaditya08@live.com \
--cc=asahi@lists.linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=ernesto.mnd.fernandez@gmail.com \
--cc=ernesto@corellium.com \
--cc=ethan@ethancedwards.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox