From: Yu-Chun Lin <eleanor15x@gmail.com>
To: krzysztof.kozlowski@oss.qualcomm.com
Cc: afaerber@suse.de, andrew@codeconstruct.com.au,
eleanor.lin@realtek.com, james.tai@realtek.com, joel@jms.id.au,
linusw@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-realtek-soc@lists.infradead.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH 4/4] ARM: realtek: MAINTAINERS: Include pin controller drivers
Date: Mon, 13 Apr 2026 21:57:56 +0800 [thread overview]
Message-ID: <20260413135756.8796-1-eleanor15x@gmail.com> (raw)
In-Reply-To: <e483acb6-af9d-4bc4-9aa6-c4841ff0a8dc@oss.qualcomm.com>
> On 13/04/2026 11:23, Yu-Chun Lin [林祐君] wrote:
>>> No dedicated maintainers are shown for Realtek SoC pin controllers, except
>>> pinctrl subsystem maintainer, which means reduced review and impression of
>>> abandoned drivers. Pin controller drivers are essential part of an SoC, so in
>>> case of lack of dedicated entry at least cover it by the SoC platform
>>> maintainers.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>>
>>> ---
>>>
>>> This patch should go via Realtek SoC maintainers, not pinctrl.
>>> ---
>>> MAINTAINERS | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 10d12b51b1f6..374ce55e4fb6 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -3373,6 +3373,7 @@ F:
>>> Documentation/devicetree/bindings/arm/realtek.yaml
>>> F: arch/arm/boot/dts/realtek/
>>> F: arch/arm/mach-realtek/
>>> F: arch/arm64/boot/dts/realtek/
>>> +F: drivers/pinctrl/realtek/
>>>
>>> ARM/RISC-V/RENESAS ARCHITECTURE
>>> M: Geert Uytterhoeven <geert+renesas@glider.be>
>>>
>>> --
>>> 2.51.0
>>
>> Acked-by: Yu-Chun Lin <eleanor.lin@realtek.com>
>
> So James will pick it up?
>
> Best regards,
> Krzysztof
Sorry for the confusion. I'll pick up this patch and include it in a series
along with the maintainer updates and other DTS changes. I plan to submit
the series to soc@ during the v7.1-rc1 to v7.1-rc5 window.
Best regards,
Yu-Chun
prev parent reply other threads:[~2026-04-13 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 13:04 [PATCH 0/4] pinctrl: More compile testing Krzysztof Kozlowski
2026-04-10 13:04 ` [PATCH 1/4] pinctrl: realtek: Enable " Krzysztof Kozlowski
2026-04-13 9:49 ` Yu-Chun Lin [林祐君]
2026-04-10 13:04 ` [PATCH 2/4] pinctrl: aspeed: Enable compile testing outside of ARCH_ASPEED Krzysztof Kozlowski
2026-04-10 13:04 ` [PATCH 3/4] pinctrl: vt8500: Enable compile testing Krzysztof Kozlowski
2026-04-10 21:22 ` Sander Vanheule
2026-04-13 11:12 ` Krzysztof Kozlowski
2026-04-10 13:04 ` [PATCH 4/4] ARM: realtek: MAINTAINERS: Include pin controller drivers Krzysztof Kozlowski
2026-04-13 9:23 ` Yu-Chun Lin [林祐君]
2026-04-13 11:13 ` Krzysztof Kozlowski
2026-04-13 13:57 ` Yu-Chun Lin [this message]
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=20260413135756.8796-1-eleanor15x@gmail.com \
--to=eleanor15x@gmail.com \
--cc=afaerber@suse.de \
--cc=andrew@codeconstruct.com.au \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=openbmc@lists.ozlabs.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