Skip to content

gpiolib: legacy: Allow *gpio_request_one() to die independently

Andy Shevchenko linux-gpio lkml 1 version Applied

Status from this message: Applied, thanks!

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2gpiolib: legacy: Make sure we kill gpio_request_one() firstdrivers/gpio/gpiolib-legacy.c+4 -140 replies
2/2gpiolib: legacy: Allow to kill devm_gpio_request_one() independentlydrivers/gpio/gpiolib-legacy.c+12 -140 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH v1 0/2] gpiolib: legacy: Allow *gpio_request_one() to die independently

Allow *gpio_request_one() to die independently and make sure the gpio_request_one() gone first (before gpio_request() removal). Currently the devm_gpio_request_one() depends on gpio_request_one(). Open code the latter in the former to break the dependency. Also convert the latter to use legacy APIs, so we can kill it first as it's not only the logical move, but an easier task due to less amount of the leftover users in the kernel.

Besides that, we gain a few LoCs with this small refactoring, which I consider a positive change alone.

Andy Shevchenko (2):
gpiolib: legacy: Make sure we kill gpio_request_one() first
gpiolib: legacy: Allow to kill devm_gpio_request_one() independently

 drivers/gpio/gpiolib-legacy.c | 44 +++++++++++++----------------------
 1 file changed, 16 insertions(+), 28 deletions(-)
Signature · 1 line
2.50.1