From: Matthew Wilcox <willy@infradead.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [RFC] Maintainership of the EFS filesystem
Date: Sat, 6 Jun 2026 04:44:10 +0100 [thread overview]
Message-ID: <aiOXiumEOIPOQm93@casper.infradead.org> (raw)
In-Reply-To: <CAKqfh0HhN4zzV2=WJwC4ejRQup7Q3L6MkUegC9Bc0xFmzK+Msg@mail.gmail.com>
On Fri, Jun 05, 2026 at 09:52:19PM -0500, Maxwell Doose wrote:
> Hi Christian, Al,
>
> I recently sent a patch for the EFS filesystem [1]. While writing that
> patch, which fixed code that was now incompatible with the latest GCC
> (+ an undefined variable), I discovered that the EFS filesystem was
> orphaned and without a maintainer. I inquired with Andrew Morton, the
> person who merged my patch, about potentially taking over
> maintainership for EFS. He noted that he was fine with it [2], and he
> directed me to Christian regarding this possibility. As the subject
> suggests, I'd like to take over maintainership of EFS, if it's fine
> with you all.
As I said, I don't see the point. Do you have any EFS filesystems?
Are you volunteering to do any major development on it? Why shouldn't
we just delete it?
next prev parent reply other threads:[~2026-06-06 3:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 2:52 Maxwell Doose
2026-06-06 3:44 ` Matthew Wilcox [this message]
2026-06-06 4:02 ` Maxwell Doose
2026-06-06 4:21 ` Al Viro
2026-06-06 4:28 ` Maxwell Doose
2026-06-06 5:17 ` Maxwell Doose
2026-06-07 22:50 ` Mateusz Guzik
2026-06-08 1:24 ` Maxwell Doose
2026-06-06 4:21 ` Darrick J. Wong
2026-06-06 4:32 ` Maxwell Doose
2026-06-10 7:37 ` Christian Brauner
2026-06-21 20:50 ` Maxwell Doose
2026-06-21 21:13 ` Matthew Wilcox
2026-06-21 21:23 ` Maxwell Doose
2026-06-07 20:57 ` Jori Koolstra
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=aiOXiumEOIPOQm93@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome