From: Yu-Chun Lin <eleanor15x@gmail.com>
To: krzk@kernel.org
Cc: afaerber@suse.com, arnd@arndb.de, cy.huang@realtek.com,
eleanor.lin@realtek.com, eleanor15x@gmail.com,
james.tai@realtek.com, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org,
linux-realtek-soc@lists.infradead.org, stanley_chang@realtek.com
Subject: Re: [PATCH v2] MAINTAINERS: Add maintainers for ARM/REALTEK ARCHITECTURE
Date: Sun, 12 Apr 2026 19:07:43 +0800 [thread overview]
Message-ID: <20260412110743.5634-1-eleanor15x@gmail.com> (raw)
In-Reply-To: <76e70c38-7eb4-48bb-9360-2e5c16c676b3@kernel.org>
Hi Krzysztof,
I've read maintainer-soc.rst, but I’m still a bit confused about the next
steps.
I've considered the following options:
1. I should create my own git tree (on github or on kernel.org), and send
a pull request containing this MAINTAINERS patch before next rc6.
2. I thought pull requests should normally be sent from a kernel.org git
tree, but since my name is not yet in MAINTAINERS, I assumed this particular
MAINTAINERS update should go through the soc git tree instead.
3. I was still waiting for the current maintainer (Andreas Färber) to send it,
but he has not been active since the last discussion. I checked his tree[1]
and there have been no new changes.
Could you please tell me what I should do with this MAINTAINERS patch?
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/afaerber/linux-realtek.git
Best regards,
Yu-Chun
next prev parent reply other threads:[~2026-04-12 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 7:19 Yu-Chun Lin
2026-03-19 8:00 ` Krzysztof Kozlowski
2026-03-19 10:46 ` Yu-Chun Lin [林祐君]
2026-04-12 9:07 ` Yu-Chun Lin
2026-04-12 9:14 ` Krzysztof Kozlowski
2026-04-12 11:07 ` Yu-Chun Lin [this message]
2026-04-12 11:45 ` Krzysztof Kozlowski
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=20260412110743.5634-1-eleanor15x@gmail.com \
--to=eleanor15x@gmail.com \
--cc=afaerber@suse.com \
--cc=arnd@arndb.de \
--cc=cy.huang@realtek.com \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=stanley_chang@realtek.com \
/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®