linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Claudiu Beznea <claudiu.beznea@microchip.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Oct 21 (drivers/irqchip/irq-mchp-eic.o)
Date: Thu, 21 Oct 2021 17:21:06 +0100	[thread overview]
Message-ID: <87r1cebb7x.wl-maz@kernel.org> (raw)
In-Reply-To: <bfc6fc7b-2bc3-b2b6-d65b-04805fbeb59d@infradead.org>

Hi Randy,

On Thu, 21 Oct 2021 16:26:58 +0100,
Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> On 10/21/21 12:43 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20211020:
> > 
> 
> on i386 and x86_64:
> 
> ld: drivers/irqchip/irq-meson-gpio.o:(.data+0x0): undefined reference to `platform_irqchip_probe'
> ld: drivers/irqchip/irq-mchp-eic.o:(.data+0x0): undefined reference to `platform_irqchip_probe'
> 
> Full randconfig file is attached.

Thanks for the heads up. It looks like despite the drivers advertising
being able to compile on all architectures (CONFIG_COMPILE_TEST), they
obviously don't.

I'm going to slap the "fix" below on top of the current tree.

	M.

diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
index 7038957f4a77..77887e2002db 100644
--- a/drivers/irqchip/Kconfig
+++ b/drivers/irqchip/Kconfig
@@ -407,7 +407,7 @@ config IRQ_UNIPHIER_AIDET
 
 config MESON_IRQ_GPIO
        tristate "Meson GPIO Interrupt Multiplexer"
-       depends on ARCH_MESON || COMPILE_TEST
+       depends on ARCH_MESON
        default ARCH_MESON
        select IRQ_DOMAIN_HIERARCHY
        help
@@ -611,7 +611,7 @@ config APPLE_AIC
 
 config MCHP_EIC
 	bool "Microchip External Interrupt Controller"
-	depends on ARCH_AT91 || COMPILE_TEST
+	depends on ARCH_AT91
 	select IRQ_DOMAIN
 	select IRQ_DOMAIN_HIERARCHY
 	help

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2021-10-21 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  7:43 linux-next: Tree for Oct 21 Stephen Rothwell
2021-10-21 15:26 ` linux-next: Tree for Oct 21 (drivers/irqchip/irq-mchp-eic.o) Randy Dunlap
2021-10-21 16:21   ` Marc Zyngier [this message]
2021-10-21 22:25 ` linux-next: Tree for Oct 21 (drivers/net/wireless/mediatek/mt76/sdio.o) Randy Dunlap
2021-10-21 22:45   ` Lorenzo Bianconi
2021-10-21 23:40     ` Randy Dunlap

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=87r1cebb7x.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=claudiu.beznea@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).