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-rc6
Date: Fri, 7 Mar 2025 13:32:47 +0100 [thread overview]
Message-ID: <20250307123249.28832-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following set of GPIO driver fixes for the next RC.
Thanks,
Bartosz
The following changes since commit 7eb172143d5508b4da468ed59ee857c6e5e01da6:
Linux 6.14-rc5 (2025-03-02 11:48:20 -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-rc6
for you to fetch changes up to 391b41f983bf7ff853de44704d8e14e7cc648a9b:
gpio: rcar: Fix missing of_node_put() call (2025-03-06 15:51:27 +0100)
----------------------------------------------------------------
gpio fixes for v6.14-rc6
- protect gpio-aggregator against module unload
- use raw spinlock in gpio-rcar to fix a lockdep splat
- fix OF node leak in gpio-rcar
----------------------------------------------------------------
Fabrizio Castro (1):
gpio: rcar: Fix missing of_node_put() call
Koichiro Den (1):
gpio: aggregator: protect driver attr handlers against module unload
Niklas Söderlund (1):
gpio: rcar: Use raw_spinlock to protect register access
drivers/gpio/gpio-aggregator.c | 20 +++++++++++++++++---
drivers/gpio/gpio-rcar.c | 31 ++++++++++++++++++-------------
2 files changed, 35 insertions(+), 16 deletions(-)
next reply other threads:[~2025-03-07 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 12:32 Bartosz Golaszewski [this message]
2025-03-07 21:04 ` [GIT PULL] gpio fixes for v6.14-rc6 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=20250307123249.28832-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).