From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: "Linus Walleij" <linusw@kernel.org>, "Andreas Färber" <afaerber@suse.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Jeffery <andrew@codeconstruct.com.au>,
linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Joel Stanley <joel@jms.id.au>,
linux-realtek-soc@lists.infradead.org,
James Tai <james.tai@realtek.com>,
Yu-Chun Lin <eleanor.lin@realtek.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH 2/4] pinctrl: aspeed: Enable compile testing outside of ARCH_ASPEED
Date: Fri, 10 Apr 2026 15:04:57 +0200 [thread overview]
Message-ID: <20260410-pinctrl-testing-v1-2-6f708c855867@oss.qualcomm.com> (raw)
In-Reply-To: <20260410-pinctrl-testing-v1-0-6f708c855867@oss.qualcomm.com>
Since inception in commit 4d3d0e4272d8 ("pinctrl: Add core support for
Aspeed SoCs"), the Aspeed pin controller drivers cannot be compile
tested, unless ARCH_ASPEED is selected. . That partially defeats the
purpose of compile testing, since ARCH_ASPEED is pulled when building
platform kernels.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
---
drivers/pinctrl/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/Makefile b/drivers/pinctrl/Makefile
index b054cfb99348..9320ffae5f31 100644
--- a/drivers/pinctrl/Makefile
+++ b/drivers/pinctrl/Makefile
@@ -66,7 +66,7 @@ obj-$(CONFIG_PINCTRL_ZYNQMP) += pinctrl-zynqmp.o
obj-$(CONFIG_PINCTRL_ZYNQ) += pinctrl-zynq.o
obj-y += actions/
-obj-$(CONFIG_ARCH_ASPEED) += aspeed/
+obj-$(CONFIG_PINCTRL_ASPEED) += aspeed/
obj-y += bcm/
obj-$(CONFIG_PINCTRL_BERLIN) += berlin/
obj-y += cirrus/
--
2.51.0
next prev parent reply other threads:[~2026-04-10 13:05 UTC|newest]
Thread overview: 5+ 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-10 13:04 ` Krzysztof Kozlowski [this message]
2026-04-10 13:04 ` [PATCH 3/4] pinctrl: vt8500: " Krzysztof Kozlowski
2026-04-10 13:04 ` [PATCH 4/4] ARM: realtek: MAINTAINERS: Include pin controller drivers Krzysztof Kozlowski
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=20260410-pinctrl-testing-v1-2-6f708c855867@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.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=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