From: Paul Cercueil <paul@crapouillou.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Paul Burton <paul.burton@mips.com>,
linux-mips@vger.kernel.org,
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>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>
Subject: Re: linux-next: Tree for Aug 19 (irqchip: irq-ingenic-tcu.c)
Date: Tue, 20 Aug 2019 00:11:35 +0200 [thread overview]
Message-ID: <1566252695.2037.0@crapouillou.net> (raw)
In-Reply-To: <ebcc8c55-3e77-bd3e-fa39-fed48d129250@infradead.org>
Hi Randy,
The fix was merged a couple of hours ago in mips-next.
Cheers
-Paul
Le mar. 20 août 2019 à 0:06, Randy Dunlap <rdunlap@infradead.org> a
écrit :
> On 8/19/19 2:18 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20190816:
>>
>
> on i386:
>
> ld: drivers/irqchip/irq-ingenic-tcu.o: in function
> `ingenic_tcu_intc_cascade':
> irq-ingenic-tcu.c:(.text+0xb1): undefined reference to
> `irq_get_domain_generic_chip'
> ld: drivers/irqchip/irq-ingenic-tcu.o: in function
> `ingenic_tcu_irq_init':
> irq-ingenic-tcu.c:(.init.text+0x91): undefined reference to
> `irq_generic_chip_ops'
> ld: irq-ingenic-tcu.c:(.init.text+0xd2): undefined reference to
> `__irq_alloc_domain_generic_chips'
> ld: irq-ingenic-tcu.c:(.init.text+0xfb): undefined reference to
> `irq_get_domain_generic_chip'
>
>
> Full randconfig file is attached.Jason Cooper <jason@lakedaemon.net>
>
>
> --
> ~Randy
next prev parent reply other threads:[~2019-08-19 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 9:18 linux-next: Tree for Aug 19 Stephen Rothwell
2019-08-19 21:53 ` linux-next: Tree for Aug 19 (gpu/drm/amd/display/) Randy Dunlap
2019-08-19 22:06 ` linux-next: Tree for Aug 19 (irqchip: irq-ingenic-tcu.c) Randy Dunlap
2019-08-19 22:11 ` Paul Cercueil [this message]
2019-08-20 1:34 ` linux-next: Tree for Aug 19 (amdgpu) Randy Dunlap
2019-08-20 1:45 ` Stephen Rothwell
2019-08-20 12:36 ` Jason Gunthorpe
2019-08-21 15:34 ` Kuehling, Felix
2019-08-21 16:10 ` Jason Gunthorpe
2019-08-20 1:57 ` linux-next: Tree for Aug 19 (amdgpu #2) Randy Dunlap
2019-08-20 4:16 ` linux-next: Tree for Aug 19 (drivers/net/netdevsim/dev.o) Randy Dunlap
2019-08-20 14:13 ` Ido Schimmel
2019-08-20 18:13 ` Ido Schimmel
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=1566252695.2037.0@crapouillou.net \
--to=paul@crapouillou.net \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@kernel.org \
--cc=paul.burton@mips.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