Re: [gpio:for-next 67/67] pch_gbe_main.c:undefined reference to `devm_gpio_request_one'
From: Linus Walleij <hidden>
Date: 2013-10-25 10:49:32
Also in:
linux-gpio
Possibly related (same subject, not in this thread)
- 2013-10-31 · Re: [gpio:for-next 67/67] pch_gbe_main.c:undefined reference to `devm_gpio_request_one' · David Cohen <hidden>
- 2013-10-30 · Re: [gpio:for-next 67/67] pch_gbe_main.c:undefined reference to `devm_gpio_request_one' · Linus Walleij <hidden>
- 2013-10-28 · Re: [gpio:for-next 67/67] pch_gbe_main.c:undefined reference to `devm_gpio_request_one' · David Cohen <hidden>
- 2013-10-28 · Re: [gpio:for-next 67/67] pch_gbe_main.c:undefined reference to `devm_gpio_request_one' · Darren Hart <hidden>
- 2013-10-27 · Re: [gpio:for-next 67/67] pch_gbe_main.c:undefined reference to `devm_gpio_request_one' · David Cohen <hidden>
On Fri, Oct 25, 2013 at 12:41 PM, Linus Walleij [off-list ref] wrote:
quoted
I wouldn't object to adding a dependency to GPIO_PCH and GPIOLIB unconditionally for PCH_GBE as GPIO_PCH is the same chip... but I don't know if David Miller would be amenable to that.Well we should probably just stick a dependency to GPIOLIB in there. - It #includes <linux/gpio.h> - It uses gpiolib functions to do something vital It was just happy that dummy versions were slotted in until now.
...or maybe I'm just confused now? Should we just add a static inline stub of devm_gpio_request_one()? Yours, Linus Walleij