[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdbOeSDEx0ms_VMPSdB=5qrfhNVPWs-neL+sVMydVy-E-A@mail.gmail.com>
Date: Mon, 12 Sep 2016 15:27:07 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Marc Zyngier <marc.zyngier@....com>
Subject: Re: linux-next: build failure after merge of the gpio tree
On Fri, Sep 9, 2016 at 6:36 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/gpio/gpiolib.c: In function '_gpiochip_irqchip_add':
> drivers/gpio/gpiolib.c:1622:62: error: macro "WARN_ON" passed 3 arguments, but takes just 1
> "%s: Ignoring %d default trigger\n", of_node->full_name))
> ^
> drivers/gpio/gpiolib.c:1621:6: error: 'WARN_ON' undeclared (first use in this function)
> if (WARN_ON(of_node && type != IRQ_TYPE_NONE,
> ^
>
> Caused by commit
>
> 1ded8b1dafe6 ("gpio/gpiolib: Forbid irqchip default trigger if probed over DT")
>
> I used the version of the gpio tree from next-20160908 for today.
Sorry about this, fixed it up.
Yours,
Linus Walleij
Powered by blists - more mailing lists