From: Conor Dooley <conor@kernel.org>
To: linusw@kernel.org
Cc: conor@kernel.org, linux-gpio@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH] pinctrl: fix kismet issues with GENERIC_PINCTRL
Date: Fri, 30 Jan 2026 23:55:30 +0000 [thread overview]
Message-ID: <20260130-stoop-gleeful-29f2c525bd48@spud> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
lkp reported that GENERIC_PINCTRL can be select when its dependencies
are not. Swap the "depends on" out for "select", as is used in other
parts of the pinctrl core that are expected to be selected by drivers.
Fixes: 43722575e5cd ("pinctrl: add generic functions + pins mapper")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202601271725.gqlQ8Jl7-lkp@intel.com/
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
drivers/pinctrl/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
index 6cc5e214f4f3..afecd9407f53 100644
--- a/drivers/pinctrl/Kconfig
+++ b/drivers/pinctrl/Kconfig
@@ -27,9 +27,9 @@ config GENERIC_PINCONF
config GENERIC_PINCTRL
bool
- depends on GENERIC_PINCONF
- depends on GENERIC_PINCTRL_GROUPS
- depends on GENERIC_PINMUX_FUNCTIONS
+ select GENERIC_PINCONF
+ select GENERIC_PINCTRL_GROUPS
+ select GENERIC_PINMUX_FUNCTIONS
config DEBUG_PINCTRL
bool "Debug PINCTRL calls"
--
2.51.0
next reply other threads:[~2026-01-30 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 23:55 Conor Dooley [this message]
2026-02-03 0:03 ` [PATCH] pinctrl: fix kismet issues with GENERIC_PINCTRL 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=20260130-stoop-gleeful-29f2c525bd48@spud \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.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