[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACxGe6uaxKoqKVyVZsaXZ6s-J3urJ7i_SxP2S-6sXQ7ZqXrYFw@mail.gmail.com>
Date: Fri, 3 Feb 2012 16:18:08 -0700
From: Grant Likely <grant.likely@...retlab.ca>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: linux-next: build failure after merge of the gpio tree
On Thu, Feb 2, 2012 at 7:54 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Grant,
>
> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/i2c/busses/i2c-gpio.c:18:22: fatal error: asm/gpio.h: No such file or directory
> drivers/input/mouse/gpio_mouse.c:17:22: fatal error: asm/gpio.h: No such file or directory
> drivers/leds/leds-gpio.c:23:22: fatal error: asm/gpio.h: No such file or directory
>
> Caused by commit 4f79dfb562c2 ("gpiolib/arches: Centralise bolierplate
> asm/gpio.h"). Grep is your friend ...
>
> I have used the gpio tree from next-20120202 for today.
I've dropped the patch from my tree. Looks like there are still a few
drivers that need to be either fixed up or made "depends on
ARCH_HAVE_CUSTOM_GPIO_H".
g.
--
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