From: Nick Chan <towinchenmi@gmail.com>
To: Hector Martin <marcan@marcan.st>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, asahi@lists.linux.dev, soc@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Remove myself
Date: Fri, 7 Feb 2025 14:13:32 +0800 [thread overview]
Message-ID: <f48c3c74-5693-40b9-a869-577e2fbb5069@gmail.com> (raw)
In-Reply-To: <20250207-rm-maint-v1-1-10f069a24f3d@marcan.st>
Hector Martin 於 2025/2/7 凌晨2:21 寫道:
> 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.
Hi marcan,
It is sad to see you go, I believe there are issues in the kernel development process as well.
Aside from Apple Silicon Macs, your work has greatly simplified the work
required for booting Linux on iPhones and iPads. However, Sven Peter is still listed as
maintainer, so for upstream purposes, will the https://github.com/asahilinux/linux tree be used
in the future, or perhaps the tree should be removed from the MAINTAINERS file as well?
Nick Chan
next prev parent reply other threads:[~2025-02-07 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 18:21 [PATCH] MAINTAINERS: Remove myself Hector Martin
2025-02-06 18:46 ` Neal Gompa
2025-02-07 6:13 ` Nick Chan [this message]
2025-02-07 14:51 ` Evelyn Harthbrooke
2025-02-14 15:10 ` patchwork-bot+linux-soc
2025-02-21 17:05 ` Hector Martin
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 7:19 Sven Peter
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=f48c3c74-5693-40b9-a869-577e2fbb5069@gmail.com \
--to=towinchenmi@gmail.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