On Wed, Jun 26, 2013 at 12:50 PM, Javier Martinez Canillas
<[email protected]> wrote:

[...]

> Aaro, could you please test if these changes break any of your OMAP1 boards?
> Although it shouldn't do it as far as I can tell.

This doesn't build for omap1_defconfig (at least in next-20130702):

/work/kernel/next/drivers/gpio/gpio-omap.c: In function 'omap_gpio_chip_init':
/work/kernel/next/drivers/gpio/gpio-omap.c:1080:17: error: 'struct
gpio_chip' has no member named 'of_node'
/work/kernel/next/drivers/gpio/gpio-omap.c: In function 'omap_gpio_irq_map':
/work/kernel/next/drivers/gpio/gpio-omap.c:1116:16: error: 'struct
gpio_chip' has no member named 'of_node'

Probably because OMAP1 is non-DT?

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to