From: Fange Zhang <fange.zhang@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dmitry.baryshkov@oss.qualcomm.com,
tingwei.zhang@oss.qualcomm.com, xiangxu.yin@oss.qualcomm.com
Subject: Re: [PATCH 2/2] arm64: defconfig: Modularize SX150X GPIO expander
Date: Mon, 18 Aug 2025 15:10:47 +0800 [thread overview]
Message-ID: <77067ec1-4f1f-45d1-8027-4c7a6f66ecff@oss.qualcomm.com> (raw)
In-Reply-To: <43e2a824-d7a3-4142-9b59-416df0c0c2c9@kernel.org>
On 8/18/2025 2:33 PM, Krzysztof Kozlowski wrote:
> On 18/08/2025 06:41, Fange Zhang wrote:
>> Modularize the SX150X GPIO expander which is equipped on the QCS615 Ride
>
> Qualcomm QCS615 Ride
>
> You are changing defconfig for all platforms, it's not your personal or
> company defconfig.
Thank you for the feedback. Yes, The change is intended to support the
Qualcomm QCS615 Ride platform, which is now upstream-ready and actively
maintained.
I believe enabling it as a module ensures it's available without
impacting other platforms. While it's not currently used directly in the
kernel, having it built as a module allows flexibility for platforms
like QCS615 that may require it in future use cases.
>
>>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-08-18 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 4:41 [PATCH 0/2] " Fange Zhang
2025-08-18 4:41 ` [PATCH 1/2] pinctrl: sx150x: Make the driver tristate Fange Zhang
2025-08-19 12:55 ` Linus Walleij
2025-08-20 2:55 ` Fange Zhang
2025-08-20 6:18 ` Krzysztof Kozlowski
2025-08-20 7:34 ` Fange Zhang
2025-08-18 4:41 ` [PATCH 2/2] arm64: defconfig: Modularize SX150X GPIO expander Fange Zhang
2025-08-18 6:33 ` Krzysztof Kozlowski
2025-08-18 7:10 ` Fange Zhang [this message]
2025-08-18 8:02 ` Krzysztof Kozlowski
2025-08-18 8:38 ` Fange Zhang
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=77067ec1-4f1f-45d1-8027-4c7a6f66ecff@oss.qualcomm.com \
--to=fange.zhang@oss.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=will@kernel.org \
--cc=xiangxu.yin@oss.qualcomm.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®