[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <82f82952-dedd-ce4f-e339-c69dac241a8a@gmail.com>
Date: Fri, 1 Sep 2017 21:49:40 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: open list <linux-kernel@...r.kernel.org>,
linux-gpio@...r.ekernel.org,
Linus Walleij <linus.walleij@...aro.org>
Cc: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
Andrew Lunn <andrew@...n.ch>
Subject: Warnings from include/linux/gpio/consumer.h with CONFIG_GPIOLIB=n
Hi Linus,
I think Sergei or someone else was mentioning that before a while ago,
but when CONFIG_GPIOLIB=n most gpiod_* inline stubs have WARN_ON() that
will scare people.
What do you recommend doing for code that might be built with or without
CONFIG_GPIOLIB, should we just encapsulate the part that deals with
GPIOs under an #if IS_ENABLED(CONFIG_GPIOLIB) or something? The
particular piece of code that I just saw this with is
drivers/net/phy/mdio_bus.c.
Thanks!
--
Florian
Powered by blists - more mailing lists