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-rc7
Date: Fri, 14 Mar 2025 15:27:40 +0100 [thread overview]
Message-ID: <20250314142740.49129-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following GPIO core fixes for the next RC.
The first commit is a backport from my v6.15-rc1 queue that turned out to
be needed in v6.14 as well but as the former diverged from my fixes branch
I had to adjust the patch a bit. I will pull in v6.14-rc7 once tagged and
resolve the conflict between the two.
The second commit fixes a regression observed in user-space where closing
a file descriptor associated with a GPIO device results in a ~10ms delay
due to the atomic notifier calling rcu_synchronize() when unregistering.
Please pull,
Bartosz
The following changes since commit 80e54e84911a923c40d7bee33a34c1b4be148d7a:
Linux 6.14-rc6 (2025-03-09 13:45:25 -1000)
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-rc7
for you to fetch changes up to dcb73cbaaeb39c9fd00bf2e019f911725945e2fe:
gpio: cdev: use raw notifier for line state events (2025-03-13 09:20:12 +0100)
----------------------------------------------------------------
gpio fixes for v6.14-rc7
- use raw notifier for line state events
- don't check the return value of gpio_chip::get_direction() when
registering a GPIO chip
----------------------------------------------------------------
Bartosz Golaszewski (2):
gpiolib: don't check the retval of get_direction() when registering a chip
gpio: cdev: use raw notifier for line state events
drivers/gpio/gpiolib-cdev.c | 15 +++++++++------
drivers/gpio/gpiolib.c | 35 ++++++++++++++++-------------------
drivers/gpio/gpiolib.h | 5 ++++-
3 files changed, 29 insertions(+), 26 deletions(-)
next reply other threads:[~2025-03-14 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 14:27 Bartosz Golaszewski [this message]
2025-03-14 21:04 ` [GIT PULL] gpio fixes for v6.14-rc7 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=20250314142740.49129-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;
as well as URLs for NNTP newsgroup(s).