Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: WfECXPTZrihgDei06/vGXXmZpLSRbt2S95+EyMkkSgCbWTLqScwy33VYmjqKYjamKVJn0ZBEqm
 6QBp8tz0q+I1M1Bceuy/vf4wMtlUjqQp5JtyYUhR7eOFgySXJqASAnPKOJZZLLq/mDuKM6KyDk
 WYDlZT8/D+09Sx54kk2qcAqG2peu6UvBfF1DFpSF4HbineKFc7G416yFz7z6DHcPhJ0lyYvFof
 7q2tUKuhB+J8TufPhTA1CSjQD4jutE7dY2Kn7yDIiM4WI9ThQA5e+s1pyUwazenDBZMOokzYh4
 qic=
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
Thread-Topic: Getting a new fs in the kernel
Thread-Index: AQHW8///osNsQgyXb0SMzho9ts3DIg==
Date:   Tue, 26 Jan 2021 19:06:55 +0000
Message-ID: <BYAPR04MB4965F2E2624369B34346CC5686BC9@BYAPR04MB4965.namprd04.prod.outlook.com>
References: <CAE1WUT7xJyx_gbxJu3r9DJGbqSkWZa-moieiDWC0bue2CxwAwg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7fb7ef1f-d23a-47e6-d495-08d8c22d8c59
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jan 2021 19:06:55.5550
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: z0guGezbuRVjxwd8LhvGYFgrhYTk8qUxWi16NuGS4jAIE/9X73OYlZVAt248Xk4JDxm26z+MWd2iSf1kq1O6fu+/HEpXxYqZ0onBBAj/Qtw=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR04MB5895
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Amy,=0A=
=0A=
On 1/26/21 8:26 AM, Amy Parker wrote:=0A=
> Kernel development newcomer here. I've begun creating a concept for a=0A=
> new filesystem, and ideally once it's completed, rich, and stable I'd=0A=
> try to get it into the kernel.=0A=
>=0A=
> What would be the process for this? I'd assume a patch sequence, but=0A=
> they'd all be dependent on each other, and sending in tons of=0A=
> dependent patches doesn't sound like a great idea. I've seen requests=0A=
> for pulls, but since I'm new here I don't really know what to do.=0A=
>=0A=
> Thank you for guidance!=0A=
>=0A=
> Best regards,=0A=
> Amy Parker=0A=
> she/her/hers=0A=
>=0A=
From what I've seen you can post the long patch-series as an RFC and get th=
e=0A=
=0A=
discussion started.=0A=
=0A=
The priority should be ease of review and not the total patch-count.=0A=
=0A=
=0A=