From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
brgl@kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: [GIT PULL] gpio fixes for v7.2-rc6
Date: Thu, 30 Jul 2026 09:50:24 +0200 [thread overview]
Message-ID: <20260730075024.7320-1-bartosz.golaszewski@oss.qualcomm.com> (raw)
Linus,
Please pull the following set of GPIO fixes for the next RC.
Thanks,
Bartosz
The following changes since commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa:
Linux 7.2-rc3 (2026-07-12 14:16:39 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v7.2-rc6
for you to fetch changes up to a02b8950d619123da64f69b70fe1dadef217dfe4:
gpio: pch: use raw_spinlock_t for the register lock (2026-07-27 15:07:51 +0200)
----------------------------------------------------------------
gpio fixes for v7.2-rc6
- fix a memory leak in gpio-sloppy-logic-analyzer
- fix a regression in GPIO hog handling for hogs without direction
specified
- extend the critical section in IRQ handling in gpio-pca953x to cover
the reads from the direction register
- disable the interrupt on errors when restoring context in gpio-pca953x
- apply the initial value when setting direction in gpio-by-pinctrl
- use raw spinlock for the register lock in gpio-pch to address locking
context issues
----------------------------------------------------------------
Abdun Nihaal (1):
gpio: sloppy-logic-analyzer: Fix memory leak in gpio_la_poll_probe()
Alex Tran (1):
gpio: gpio-by-pinctrl: Apply initial value in direction output wrapper
Daniel Golle (1):
gpiolib: tolerate gpio-hogs lacking a hogging state
Junjie Cao (1):
gpio: pch: use raw_spinlock_t for the register lock
Mark Tomlinson (1):
gpio: pca953x: fix pca953x_irq_bus_sync_unlock regmap lock
bui duc phuc (1):
gpio: pca953x: fix cache_only and IRQ state on restore_context() failure
drivers/gpio/gpio-by-pinctrl.c | 18 ++++++++++------
drivers/gpio/gpio-pca953x.c | 34 ++++++++++++++++++++++++-------
drivers/gpio/gpio-pch.c | 28 ++++++++++++-------------
drivers/gpio/gpio-sloppy-logic-analyzer.c | 10 +++++++++
drivers/gpio/gpiolib.c | 13 +++++++-----
5 files changed, 71 insertions(+), 32 deletions(-)
next reply other threads:[~2026-07-30 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 7:50 Bartosz Golaszewski [this message]
2026-07-30 19:14 ` 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=20260730075024.7320-1-bartosz.golaszewski@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.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
all inboxes | Powered by JetHome®