[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151002133751.739bb08c@canb.auug.org.au>
Date: Fri, 2 Oct 2015 13:37:51 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Ludovic Desroches <ludovic.desroches@...el.com>
Subject: Re: linux-next: build failure after merge of the pinctrl tree
Hi Linus,
On Fri, 25 Sep 2015 13:34:10 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the pinctrl tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/pinctrl/pinctrl-at91-pio4.c: In function 'atmel_gpio_irq_set_type':
> drivers/pinctrl/pinctrl-at91-pio4.c:170:3: error: implicit declaration of function '__irq_set_handler_locked' [-Werror=implicit-function-declaration]
> __irq_set_handler_locked(d->irq, handle_edge_irq);
> ^
> drivers/pinctrl/pinctrl-at91-pio4.c: In function 'atmel_pinctrl_probe':
> drivers/pinctrl/pinctrl-at91-pio4.c:925:3: warning: passing argument 2 of 'irq_set_chained_handler' from incompatible pointer type
> irq_set_chained_handler(res->start, atmel_gpio_irq_handler);
> ^
> In file included from include/linux/gpio/driver.h:6:0,
> from include/asm-generic/gpio.h:12,
> from arch/arm/include/asm/gpio.h:9,
> from include/linux/gpio.h:48,
> from drivers/pinctrl/pinctrl-at91-pio4.c:18:
> include/linux/irq.h:548:1: note: expected 'irq_flow_handler_t' but argument is of type 'void (*)(unsigned int, struct irq_desc *)'
> irq_set_chained_handler(unsigned int irq, irq_flow_handler_t handle)
> ^
>
> Caused by commit
>
> 776180848b57 ("pinctrl: introduce driver for Atmel PIO4 controller")
>
> I have used the pinctrl tree from next-20150924 for today.
I am still getting this error.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists