[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9235D6609DB808459E95D78E17F2E43D40B1B424@CHN-SV-EXMX02.mchp-main.com>
Date: Thu, 7 Sep 2017 21:30:26 +0000
From: <Woojung.Huh@...rochip.com>
To: <linus.walleij@...aro.org>, <andrew@...n.ch>
CC: <festevam@...il.com>, <sergei.shtylyov@...entembedded.com>,
<davem@...emloft.net>, <f.fainelli@...il.com>,
<netdev@...r.kernel.org>, <fabio.estevam@....com>
Subject: RE: [PATCH net-next] mdio_bus: Remove unneeded gpiod NULL check
> If someone is using GPIO descriptors with GPIO disabled, i.e. calling
> gpiod_get() and friends, this is very likely to be a bug, and what
> the driver wants to do is:
>
> depends on GPIOLIB
>
> or
>
> select GPIOLIB
>
> in Kconfig. The whole optional thing is mainly a leftover from when it
> was possible to have a local implementation of the GPIOLIB API in
> some custom header file, noone sane should be doing that anymore,
> and if they do, they can very well face the warnings.
>
> If someone is facing a lot of WARN_ON() messages to this, it is a clear
> indication that they need to fix their Kconfig and in that case it is proper.
Linus & Andrew,
I knew that it is already in David's pulling request.
Configuring GPIOLIB is the right solution even if platform doesn't use it?
Did I miss any new patch?
Thanks.
Woojung
Powered by blists - more mailing lists