From: "Arnd Bergmann" <arnd@arndb.de>
To: "Julian Braha" <julianbraha@gmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Andrea della Porta" <andrea.porta@suse.com>
Cc: "Phil Elwell" <phil@raspberrypi.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
iivanov@suse.de, joshua.henderson@microchip.com,
"Lee Jones" <lee@kernel.org>,
amelie.delaunay@st.com, "Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
yrdreddy@broadcom.com,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pinctrl: fix unmet dependencies from missing GPIOLIB
Date: Thu, 16 Jul 2026 15:21:32 +0200 [thread overview]
Message-ID: <64117177-84e6-497a-9c3e-4361a11c4922@app.fastmail.com> (raw)
In-Reply-To: <20260716131626.103199-1-julianbraha@gmail.com>
On Thu, Jul 16, 2026, at 15:16, Julian Braha wrote:
> These 4 options, PINCTRL_PIC32, PINCTRL_STMFX, PINCTRL_IPROC_GPIO, and
> PINCTRL_NSP_GPIO all select GPIOLIB_IRQCHIP without ensuring GPIOLIB is
> enabled, causing unmet dependencies, such as:
>
> WARNING: unmet direct dependencies detected for GPIOLIB_IRQCHIP
> Depends on [n]: GPIOLIB [=n]
> Selected by [y]:
> - PINCTRL_PIC32 [=y] && PINCTRL [=y] && OF [=y] && (MACH_PIC32 ||
> COMPILE_TEST [=y])
>
> Similar options in this subsystem select GPIOLIB, so let's do the same here.
>
> These unmet dependency bugs were found by kconfirm, a static analysis tool for
> Kconfig.
>
> Fixes: 2ba384e6c381 ("pinctrl: pinctrl-pic32: Add PIC32 pin control
> driver")
> Fixes: 1490d9f841b1 ("pinctrl: Add STMFX GPIO expander Pinctrl/GPIO
> driver")
> Fixes: b64333ce769c ("pinctrl: cygnus: add gpio/pinconf driver")
> Fixes: 8bfcbbbcabe0 ("pinctrl: nsp: add gpio-a driver support for
> Broadcom NSP SoC")
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2026-07-16 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 13:16 Julian Braha
2026-07-16 13:21 ` Arnd Bergmann [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=64117177-84e6-497a-9c3e-4361a11c4922@app.fastmail.com \
--to=arnd@arndb.de \
--cc=amelie.delaunay@st.com \
--cc=andrea.porta@suse.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=iivanov@suse.de \
--cc=joshua.henderson@microchip.com \
--cc=julianbraha@gmail.com \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=yrdreddy@broadcom.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
all inboxes | Powered by JetHome®