Here's a set of fixes to issues spotted in next after queuing the series
adding return value sanitization to GPIO core.

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
Changes in v2:
- add a comment to patch 1/3
- rework the retval logic even more in patch 2/3
- Link to v1: https://lore.kernel.org/r/20250225-retval-fixes-v1-0-078c4c98517a@linaro.org

---
Bartosz Golaszewski (3):
      gpiolib: don't use gpiochip_get_direction() when registering a chip
      gpiolib: use a more explicit retval logic in gpiochip_get_direction()
      gpiolib: don't double-check the gc->get callback's existence

 drivers/gpio/gpiolib.c | 38 +++++++++++++++++---------------------
 1 file changed, 17 insertions(+), 21 deletions(-)
---
base-commit: 0226d0ce98a477937ed295fb7df4cc30b46fc304
change-id: 20250225-retval-fixes-a1a09a1e3a08

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>


On Wed, 26 Feb 2025 11:12:28 +0100, Bartosz Golaszewski wrote:
> Here's a set of fixes to issues spotted in next after queuing the series
> adding return value sanitization to GPIO core.
> 
> 

Applied, thanks!

[1/3] gpiolib: don't use gpiochip_get_direction() when registering a chip
      commit: 9becde08f1bc2857cd66f847eca2aaec3fc05c21
[2/3] gpiolib: use a more explicit retval logic in gpiochip_get_direction()
      commit: cc78604fd4799a8e8e9d23ea4898acd6b605982d
[3/3] gpiolib: don't double-check the gc->get callback's existence
      commit: 8a5680bffb2f681688b5788751c767fc380ff9b7

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>