gpiolib: legacy: Allow *gpio_request_one() to die independently
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | gpiolib: legacy: Make sure we kill gpio_request_one() firstdrivers/ | +4 | 0 replies | |
| 2/2 | gpiolib: legacy: Allow to kill devm_gpio_request_one() independentlydrivers/ | +12 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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