The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio fixes for v6.14-rc4
Date: Fri, 21 Feb 2025 15:47:50 +0100	[thread overview]
Message-ID: <20250221144750.108147-1-brgl@bgdev.pl> (raw)

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

Linus,

Please pull the following set of GPIO fixes for the upcoming RC. There
are two fixes for GPIO core: one adds missing retval checks to older
code, while the second adds SRCU synchronization to legs in code that
were missed during the big rework a few cycles back. There's also one
small driver fix.

Best Regards,
Bartosz Golaszewski

The following changes since commit 0ad2507d5d93f39619fc42372c347d6006b64319:

  Linux 6.14-rc3 (2025-02-16 14:02:44 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.14-rc4

for you to fetch changes up to 96fa9ec477ff60bed87e1441fd43e003179f3253:

  gpiolib: don't bail out if get_direction() fails in gpiochip_add_data() (2025-02-20 14:08:18 +0100)

----------------------------------------------------------------
gpio fixes for v6.14-rc4

- check the return value of the get_direction() callback in struct
  gpio_chip
- protect the multi-line get/set legs in GPIO core with SRCU
- fix a race condition in gpio-vf610

----------------------------------------------------------------
Bartosz Golaszewski (3):
      gpiolib: check the return value of gpio_chip::get_direction()
      gpiolib: protect gpio_chip with SRCU in array_info paths in multi get/set
      gpiolib: don't bail out if get_direction() fails in gpiochip_add_data()

Johan Korsnes (1):
      gpio: vf610: add locking to gpio direction functions

 drivers/gpio/gpio-vf610.c |   4 ++
 drivers/gpio/gpiolib.c    | 100 ++++++++++++++++++++++++++++++++--------------
 drivers/gpio/gpiolib.h    |   4 +-
 3 files changed, 76 insertions(+), 32 deletions(-)

             reply	other threads:[~2025-02-21 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 14:47 Bartosz Golaszewski [this message]
2025-02-21 17:10 ` [GIT PULL] gpio fixes for v6.14-rc4 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250221144750.108147-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox