From: Brian Masney <bmasney@redhat.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Joshua Henderson <joshua.henderson@microchip.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Masney <bmasney@redhat.com>
Subject: [PATCH 3/3] pinctrl: pic32: allow driver to be compiled with COMPILE_TEST
Date: Sun, 22 Feb 2026 18:33:31 -0500 [thread overview]
Message-ID: <20260222-pinctrl-pic32-v1-3-db86248da18d@redhat.com> (raw)
In-Reply-To: <20260222-pinctrl-pic32-v1-0-db86248da18d@redhat.com>
This driver currently only supports builds against a PIC32 target. Now
that commit b8694faa1a0f ("pinctrl: pic32: update include to use pic32.h
from platform_data") is merged, it's possible to compile this driver on
other architectures.
To avoid future breakage of this driver in the future, let's update the
Kconfig so that it can be built with COMPILE_TEST enabled on all
architectures.
Signed-off-by: Brian Masney <bmasney@redhat.com>
---
drivers/pinctrl/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
index afecd9407f5354f5b92223f8cd80d2f7a08f8e7d..1965d4fb461d93cb486e80864cee61fc5acc9ab4 100644
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
@@ -478,7 +478,7 @@ config PINCTRL_PEF2256
config PINCTRL_PIC32
bool "Microchip PIC32 pin controller driver"
depends on OF
- depends on MACH_PIC32
+ depends on MACH_PIC32 || COMPILE_TEST
select PINMUX
select GENERIC_PINCONF
select GPIOLIB_IRQCHIP
--
2.53.0
next prev parent reply other threads:[~2026-02-22 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 23:33 [PATCH 0/3] " Brian Masney
2026-02-22 23:33 ` [PATCH 1/3] pinctrl: pic32: change all cases of bare 'unsigned' to 'unsigned int' Brian Masney
2026-02-22 23:33 ` [PATCH 2/3] pinctrl: pic32: use consistent spacing around '+' Brian Masney
2026-02-22 23:33 ` Brian Masney [this message]
2026-02-23 9:50 ` [PATCH 0/3] pinctrl: pic32: allow driver to be compiled with COMPILE_TEST Bartosz Golaszewski
2026-02-24 9:25 ` Linus Walleij
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=20260222-pinctrl-pic32-v1-3-db86248da18d@redhat.com \
--to=bmasney@redhat.com \
--cc=brgl@kernel.org \
--cc=joshua.henderson@microchip.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®