From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Amy Parker <enbyamy@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Getting a new fs in the kernel
Date: Tue, 26 Jan 2021 19:06:55 +0000 [thread overview]
Message-ID: <BYAPR04MB4965F2E2624369B34346CC5686BC9@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: CAE1WUT7xJyx_gbxJu3r9DJGbqSkWZa-moieiDWC0bue2CxwAwg@mail.gmail.com
Amy,
On 1/26/21 8:26 AM, Amy Parker wrote:
> Kernel development newcomer here. I've begun creating a concept for a
> new filesystem, and ideally once it's completed, rich, and stable I'd
> try to get it into the kernel.
>
> What would be the process for this? I'd assume a patch sequence, but
> they'd all be dependent on each other, and sending in tons of
> dependent patches doesn't sound like a great idea. I've seen requests
> for pulls, but since I'm new here I don't really know what to do.
>
> Thank you for guidance!
>
> Best regards,
> Amy Parker
> she/her/hers
>
From what I've seen you can post the long patch-series as an RFC and get the
discussion started.
The priority should be ease of review and not the total patch-count.
next prev parent reply other threads:[~2021-01-27 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 16:23 Getting a new fs in the kernel Amy Parker
2021-01-26 17:15 ` Andreas Dilger
2021-01-26 17:28 ` Amy Parker
2021-01-26 19:06 ` Chaitanya Kulkarni [this message]
2021-01-26 20:17 ` Amy Parker
2021-01-27 5:36 ` Theodore Ts'o
2021-01-28 3:21 ` Amy Parker
2021-01-26 19:06 ` Randy Dunlap
2021-01-26 19:17 ` Matthew Wilcox
2021-01-26 20:22 ` Amy Parker
2021-01-28 21:26 ` Pavel Machek
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=BYAPR04MB4965F2E2624369B34346CC5686BC9@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=enbyamy@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).