From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ethan Carter Edwards <ethan@ethancedwards.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-staging@lists.linux.dev, asahi@lists.linux.dev
Subject: Re: [RFC] apfs: thoughts on upstreaming an out-of-tree module
Date: Sun, 2 Mar 2025 13:55:17 +0300 [thread overview]
Message-ID: <b9c2ce02-dab6-4b4d-b8ca-ac1e7769e0c3@stanley.mountain> (raw)
In-Reply-To: <rxefeexzo2lol3qph7xo5tgnykp5c6wcepqewrze6cqfk22leu@wwkiu7yzkpvp>
If you're going to do a major re-work it might be easier to do that first
before you upstream it. Once it's in the kernel then you have to follow
all the rules like breaking your commits up into reviewable patches and
not breaking git bisect. The rules are good for quality control but they
can be burdensome for people who want to move fast and break things.
regards,
dan carpenter
prev parent reply other threads:[~2025-03-02 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 1:53 [RFC] apfs: thoughts on upstreaming an out-of-tree module Ethan Carter Edwards
2025-02-28 12:55 ` Theodore Ts'o
2025-03-01 16:26 ` Ethan Carter Edwards
2025-02-28 23:04 ` Sven Peter
2025-03-01 16:39 ` Ethan Carter Edwards
2025-03-05 7:23 ` Aditya Garg
2025-03-06 18:04 ` Theodore Ts'o
2025-03-06 19:39 ` Sven Peter
2025-03-07 16:50 ` Ernesto A. Fernández
2025-03-02 10:55 ` Dan Carpenter [this message]
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=b9c2ce02-dab6-4b4d-b8ca-ac1e7769e0c3@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=asahi@lists.linux.dev \
--cc=ethan@ethancedwards.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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