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
Date: Thu, 13 Aug 2026 10:17:48 +0200 [thread overview]
Message-ID: <20260813081748.9285-1-bartosz.golaszewski@oss.qualcomm.com> (raw)
Linus,
Please pull the final set of GPIO fixes for this release.
Thanks,
Bartosz
The following changes since commit db2ddb87143519e20a95aa36c60b36107b736a58:
Linux 7.2-rc7 (2026-08-09 14:54:50 -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
for you to fetch changes up to 44f3468a0aef1aabdad551898ab7cfa2a9d20e99:
gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind (2026-08-10 12:49:04 +0200)
----------------------------------------------------------------
gpio fixes for v7.2
- use raw_spinlock_t in gpio-ml-ioh to avoid locking context issues
- fix a race condition in gpio-ml-ioh by sharing the register locks
across channels
- fix a use-after-free bug in unbind path in gpio-sloppy-logic-analyzer
----------------------------------------------------------------
Bartosz Golaszewski (1):
Merge tag 'v7.2-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux into gpio/for-current
Cengiz Can (1):
gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind
Christophe Leroy (CS GROUP) (1):
gpiolib: Check gc->get_direction() before calling gpiod_get_direction()
Junjie Cao (2):
gpio: ml-ioh: use raw_spinlock_t for the register lock
gpio: ml-ioh: share the register lock across channels
drivers/gpio/gpio-ml-ioh.c | 71 +++++++++++++++++--------------
drivers/gpio/gpio-sloppy-logic-analyzer.c | 2 +-
drivers/gpio/gpiolib.c | 3 +-
3 files changed, 41 insertions(+), 35 deletions(-)
next reply other threads:[~2026-08-13 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 8:17 Bartosz Golaszewski [this message]
2026-08-13 16:42 ` 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=20260813081748.9285-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®