From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm UFS and QMP UFS PHY drivers as built-in
Date: Mon, 20 Apr 2026 14:28:43 +0800 [thread overview]
Message-ID: <aeXHm9B3u071dBZ1@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <21664acb-8fbf-4fa9-a674-982c98992df8@oss.qualcomm.com>
On Mon, Apr 20, 2026 at 11:10:28AM +0530, Kuldeep Singh wrote:
> Then it makes sense to make CONFIG_MSM_SDHCI or CONFIG_MSM_SDHCI_MSM(qcom
> specific config) as module too?
> https://elixir.bootlin.com/linux/v7.0/source/arch/arm64/configs/defconfig#L1279
>
> Not sure why it's enabled as builtin for all vendors.
For whatever reason it's enabled there, let it be. Do not make more
developers life harder please.
From what I can see, maintainers of other platforms are flexible if
built-in for some options really makes most developers life easier,
but Qualcomm folks seems to have a high standard on this.
Shawn
prev parent reply other threads:[~2026-04-20 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 3:55 [PATCH] arm64: defconfig: Enable Qualcomm UFS and QMP UFS PHY drivers as built-in Shawn Guo
2026-04-17 8:14 ` Krzysztof Kozlowski
2026-04-17 8:37 ` Shawn Guo
2026-04-17 8:44 ` Krzysztof Kozlowski
2026-04-17 10:37 ` Shawn Guo
2026-04-17 12:57 ` Krzysztof Kozlowski
2026-04-17 22:59 ` Dmitry Baryshkov
2026-04-20 5:40 ` Kuldeep Singh
2026-04-20 6:28 ` Shawn Guo [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=aeXHm9B3u071dBZ1@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.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