From: Evelyn Harthbrooke <evieluvsrainbows@icloud.com>
To: marcan@marcan.st
Cc: arnd@arndb.de, asahi@lists.linux.dev,
linux-kernel@vger.kernel.org, olof@lixom.net,
soc@lists.linux.dev, torvalds@linux-foundation.org
Subject: Re: [PATCH] MAINTAINERS: Remove myself
Date: Fri, 7 Feb 2025 07:51:22 -0700 [thread overview]
Message-ID: <ba6efae4-77d9-46aa-8f64-f8ffa119505f@icloud.com> (raw)
In-Reply-To: <20250207-rm-maint-v1-1-10f069a24f3d@marcan.st>
On Thu, Feb 6, 2025 at 1:31 PM Hector Martin <marcan@marcan.st> wrote:
>
> I no longer have any faith left in the kernel development process or
> community management approach.
>
> Apple/ARM platform development will continue downstream. If I feel like
> sending some patches upstream in the future myself for whatever subtree
> I may, or I may not. Anyone who feels like fighting the upstreaming
> fight themselves is welcome to do so.
>
This is disappointing to see; Apple/ARM support was progressing incredibly well and it's sad to see you resign as one of the subsystems' core maintainers. But based on what happened in the Rust/DMA thread, it was only a matter of time.
There are admittedly quite a few issues with the way the kernel development process works as well as how the community is managed, and I hope that it will improve with time. Hopefully your efforts will indeed continue downstream, and people will put in the effort to upstream your work with you having resigned.
I also hope that you may decide to come back in the future, if things do indeed improve.
Evelyn
next prev parent reply other threads:[~2025-02-07 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 18:21 Hector Martin
2025-02-06 18:46 ` Neal Gompa
2025-02-07 6:13 ` Nick Chan
2025-02-07 14:51 ` Evelyn Harthbrooke [this message]
2025-02-21 17:05 ` Hector Martin
2025-02-07 7:19 Sven Peter
2025-03-17 13:47 Eric W. Biederman
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=ba6efae4-77d9-46aa-8f64-f8ffa119505f@icloud.com \
--to=evieluvsrainbows@icloud.com \
--cc=arnd@arndb.de \
--cc=asahi@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=olof@lixom.net \
--cc=soc@lists.linux.dev \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®