From: Bjorn Andersson <andersson@kernel.org>
To: Sumit Garg <sumit.garg@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Linus Walleij <linusw@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-arm-msm@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: QCOM interfaces should depend on ARCH_QCOM
Date: Thu, 10 Sep 2026 21:25:34 -0500 [thread overview]
Message-ID: <178909353836.920241.11751783764687425864.b4-ty@kernel.org> (raw)
In-Reply-To: <888efe8e63b6a18fae4acd5a90a1e0e69dcdf2ca.1786012495.git.geert+renesas@glider.be>
On Thu, 06 Aug 2026 12:35:15 +0200, Geert Uytterhoeven wrote:
> The various Qualcomm firmware interfaces are only present on Qualcomm
> systems. Hence add dependencies on ARCH_QCOM, to prevent asking the
> user about them when configuring a kernel without Qualcomm SoC support.
> Make QCOM_PAS invisible instead, as it is already selected by its users
> when needed.
>
>
> [...]
Applied, thanks!
[1/1] firmware: QCOM interfaces should depend on ARCH_QCOM
commit: 8fecd3194de338bdc0c57597be61fdcf33e1832d
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-09-11 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 10:35 [PATCH] firmware: QCOM interfaces should depend on ARCH_QCOM Geert Uytterhoeven
2026-08-17 8:56 ` Konrad Dybcio
2026-08-17 8:57 ` Konrad Dybcio
2026-09-10 6:56 ` Sumit Garg
2026-09-11 2:25 ` Bjorn Andersson [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=178909353836.920241.11751783764687425864.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=johannes@sipsolutions.net \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sumit.garg@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;
as well as URLs for NNTP newsgroup(s).