From: "Yu-Chun Lin [林祐君]" <eleanor.lin@realtek.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"linusw@kernel.org" <linusw@kernel.org>,
"brgl@kernel.org" <brgl@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"afaerber@suse.com" <afaerber@suse.com>,
"TY_Chang[張子逸]" <tychang@realtek.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>,
"CY_Huang[黃鉦晏]" <cy.huang@realtek.com>,
"Stanley Chang[昌育德]" <stanley_chang@realtek.com>,
"James Tai [戴志峰]" <james.tai@realtek.com>
Subject: RE: [PATCH v2 1/4] gpio: Remove "default y" in Kconfig
Date: Tue, 5 May 2026 10:27:04 +0000 [thread overview]
Message-ID: <9f28aa58bb8c441ca7b4a0e75c2947cf@realtek.com> (raw)
In-Reply-To: <e1829cf5-c277-4e34-8bcf-addc27bfd69c@kernel.org>
> On 30/04/2026 13:23, Krzysztof Kozlowski wrote:
> > On 08/04/2026 04:52, Yu-Chun Lin wrote:
> >> Remove the default y to avoid bloating the build for non-Realtek
> >> platforms when COMPILE_TEST is enable on other platforms.
> >>
> >
> > Why isn't this driver important for Realtek SoC? This should be
> > explained, otherwise proper fix is default for ARCH_REALTEK.
>
> And you were kind of asked for it at v1...
>
> Best regards,
> Krzysztof
I was assuming our defconfig already enables this driver as built-in, so
simply dropping "default y" seemed sufficient.
I will change it 'default ARCH_REALTEK'.
Best regards,
Yu-Chun
next prev parent reply other threads:[~2026-05-05 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 2:52 [PATCH v2 0/4] gpio: realtek: Add support for Realtek DHC RTD1625 Yu-Chun Lin
2026-04-08 2:52 ` [PATCH v2 1/4] gpio: Remove "default y" in Kconfig Yu-Chun Lin
2026-04-30 11:23 ` Krzysztof Kozlowski
2026-04-30 11:24 ` Krzysztof Kozlowski
2026-05-05 10:27 ` Yu-Chun Lin [林祐君] [this message]
2026-04-08 2:52 ` [PATCH v2 2/4] dt-bindings: gpio: realtek: Add realtek,rtd1625-gpio Yu-Chun Lin
2026-04-09 7:43 ` Krzysztof Kozlowski
2026-04-08 2:52 ` [PATCH v2 3/4] gpio: realtek: Add driver for Realtek DHC RTD1625 SoC Yu-Chun Lin
2026-04-08 7:31 ` Bartosz Golaszewski
2026-04-10 9:39 ` Yu-Chun Lin [林祐君]
2026-04-19 21:19 ` Linus Walleij
2026-04-20 7:22 ` Michael Walle
2026-04-30 9:58 ` Yu-Chun Lin [林祐君]
2026-04-30 11:20 ` Michael Walle
2026-05-05 10:26 ` Yu-Chun Lin [林祐君]
2026-04-08 2:52 ` [PATCH v2 4/4] arm64: dts: realtek: Add GPIO support for RTD1625 Yu-Chun Lin
2026-04-08 7:28 ` Bartosz Golaszewski
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=9f28aa58bb8c441ca7b4a0e75c2947cf@realtek.com \
--to=eleanor.lin@realtek.com \
--cc=afaerber@suse.com \
--cc=brgl@kernel.org \
--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=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stanley_chang@realtek.com \
--cc=tychang@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