From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Marc Zyngier <maz@kernel.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the irqchip tree
Date: Thu, 8 Apr 2021 10:35:03 +0200 [thread overview]
Message-ID: <YG7AN/viDzjyncYl@latitude> (raw)
In-Reply-To: <8171969ffe92eed0013fe3900ba0526f@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On Thu, Apr 08, 2021 at 08:56:18AM +0100, Marc Zyngier wrote:
> Hi Stephen,
>
> On 2021-04-08 07:35, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the irqchip tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/irqchip/irq-wpcm450-aic.c:9:10: fatal error: asm/exception.h:
> > No such file or directory
> > 9 | #include <asm/exception.h>
> > | ^~~~~~~~~~~~~~~~~
> >
> > Caused by commit
> >
> > fead4dd49663 ("irqchip: Add driver for WPCM450 interrupt controller")
> >
> > I have used the irqchip tree from next-20210407 for today.
>
> Thanks for the heads up. I guess that's the effect of COMPILE_TEST
> which was apparently not very well tested... I'll drop it from Kconfig.
Right, sorry about that.
> Jonathan, feel free to submit something re-enabling COMPILE_TEST once
> you've worked out the missing dependencies.
I used __exception_irq_entry from asm/exception.h, like other irqchip
drivers for ARM. This macro is only defined in arch/arm and arch/arm64.
So, AFAICS, there is no right set of dependencies for COMPILE_TEST.
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-08 8:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 6:35 linux-next: build failure after merge of the irqchip tree Stephen Rothwell
2021-04-08 7:56 ` Marc Zyngier
2021-04-08 8:35 ` Jonathan Neuschäfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-29 14:31 broonie
2022-09-29 14:31 ` broonie
2022-09-29 14:40 ` Robin Murphy
2022-09-29 14:40 ` Robin Murphy
2022-09-29 16:22 ` Marc Zyngier
2022-09-29 16:22 ` Marc Zyngier
2022-07-11 5:42 Stephen Rothwell
2022-07-11 8:15 ` Marc Zyngier
2022-07-08 4:13 Stephen Rothwell
2022-07-08 7:48 ` Marc Zyngier
2021-06-22 4:15 Stephen Rothwell
2021-06-22 4:15 ` Stephen Rothwell
2020-03-23 6:59 Stephen Rothwell
2020-03-23 8:08 ` Michal Simek
2020-03-26 6:36 ` Stephen Rothwell
2020-03-26 7:06 ` Michal Simek
2018-10-08 3:06 Stephen Rothwell
2018-10-08 7:06 ` Marc Zyngier
2015-04-13 7:05 Stephen Rothwell
2015-04-13 9:10 ` Stefan Agner
2015-04-13 10:50 ` Jason Cooper
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=YG7AN/viDzjyncYl@latitude \
--to=j.neuschaefer@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.