From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/4] gpio: select GPIOLIB_IRQCHIP for various entries
Date: Thu, 22 May 2025 15:11:49 +0800 [thread overview]
Message-ID: <20250522-gpio-fix-v1-0-98ceae7c4c3c@nxp.com> (raw)
There was an effort to make irq_chip immutable for several drivers,
but kernel test robot reports build errors for:
gpio-mpc8xxx
gpio-pxa
gpio-davinci
Thanks to Bartosz for helping on this.
To avoid potential build failure with random config, select
GPIOLIB_IRQCHIP for bcm-kona, grgpio, lpc18xx, timberdale.
Build pass with:
for i in `ls arch/arm/configs`
do
echo $i
make ARCH=arm $i
make ARCH=arm zImage -j32 > /dev/null
done
And build with arm64 defconfig.
Hope all is good now.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (4):
gpio: bcm-kona: select GPIOLIB_IRQCHIP
gpio: grgpio: select GPIOLIB_IRQCHIP
gpio: lpc18xx: select GPIOLIB_IRQCHIP
gpio: timberdale: select GPIOLIB_IRQCHIP
drivers/gpio/Kconfig | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
---
base-commit: 4e9d73034196ac8ab496bb47583197b36ba13327
change-id: 20250522-gpio-fix-bea5cc4ace8f
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2025-05-22 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 7:11 Peng Fan (OSS) [this message]
2025-05-22 7:11 ` [PATCH 1/4] gpio: bcm-kona: select GPIOLIB_IRQCHIP Peng Fan (OSS)
2025-05-22 7:11 ` [PATCH 2/4] gpio: grgpio: " Peng Fan (OSS)
2025-05-22 7:11 ` [PATCH 3/4] gpio: lpc18xx: " Peng Fan (OSS)
2025-05-23 5:23 ` Vladimir Zapolskiy
2025-05-22 7:11 ` [PATCH 4/4] gpio: timberdale: " Peng Fan (OSS)
2025-05-22 8:00 ` [PATCH 0/4] gpio: select GPIOLIB_IRQCHIP for various entries Bartosz Golaszewski
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=20250522-gpio-fix-v1-0-98ceae7c4c3c@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.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®