From: "Yu-Chun Lin [林祐君]" <eleanor.lin@realtek.com>
To: "Yu-Chun Lin [林祐君]" <eleanor.lin@realtek.com>,
"afaerber@suse.de" <afaerber@suse.de>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"James Tai [戴志峰]" <james.tai@realtek.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"CY_Huang[黃鉦晏]" <cy.huang@realtek.com>,
"Stanley Chang[昌育德]" <stanley_chang@realtek.com>
Subject: RE: [PATCH v3 0/2 RESEND] arm64: dts: Add support for Kent SoC family
Date: Wed, 21 Jan 2026 10:50:51 +0000 [thread overview]
Message-ID: <d8af877bd3fb4291b0d09a80a981e6e1@realtek.com> (raw)
In-Reply-To: <20251215103157.27039-1-eleanor.lin@realtek.com>
Hi Krzysztof,
I would like to ask for guidance on how to proceed with this patch.
The listed maintainer for Realtek SoCs, Andreas Färber, seems to be inactive
(no activity since May 2023), and my recent emails to him bounced with
"Undelivered Mail Returned to Sender".
Should I resend this patch and explicitly Cc soc@kernel.org and the ARM SoC
maintainers (e.g., Arnd Bergmann) so it can be picked up directly by the SoC team?
Best regards,
Yu-Chun
next prev parent reply other threads:[~2026-01-21 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 10:31 [PATCH v3 0/2 RESEND] arm64: dts: Add support for Kent SoC family Yu-Chun Lin
2025-12-15 10:31 ` [PATCH v3 1/2 RESEND] dt-bindings: arm: realtek: Add Kent Soc family compatibles Yu-Chun Lin
2025-12-15 10:31 ` [PATCH v3 2/2 RESEND] arm64: dts: realtek: Add Kent SoC and EVB device trees Yu-Chun Lin
2026-01-05 2:30 ` [PATCH v3 0/2 RESEND] arm64: dts: Add support for Kent SoC family Yu-Chun Lin
2026-01-21 10:50 ` Yu-Chun Lin [林祐君] [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-28 9:08 Yu-Chun Lin
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=d8af877bd3fb4291b0d09a80a981e6e1@realtek.com \
--to=eleanor.lin@realtek.com \
--cc=afaerber@suse.de \
--cc=conor+dt@kernel.org \
--cc=cy.huang@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=james.tai@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=robh@kernel.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