On Thu, Sep 7, 2017 at 11:39 PM, Florian Fainelli <f.faine...@gmail.com> wrote:
> I think it means CONFIG_GPIOLIB=n in the kernel because it's not needed, > yet you run code (like drivers/net/phy/mdio_bus.c) that unconditionally > calls into GPIOLIB and attempts to configure a given GPIO if available. > This thread is actually what prompted me to write this email: Yeah I think GPIOLIB should simply be selected in KConfig then. Sent an inline patch to do that in the other reply. Maybe I should simply delete the stubs if they confuse people. It is possible to select GPIOLIB on any platform these days and get the right APIs, this used to not be the case but I fixed it a while back. Alternatively we can depend on GPIOLIB but it's simpler to just select it I think, it's like a library this code uses and so that's it. Yours, Linus Walleij
