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.1-rc5
Date: Fri, 22 May 2026 11:36:22 +0200 [thread overview]
Message-ID: <20260522093622.24099-1-bartosz.golaszewski@oss.qualcomm.com> (raw)
Linus,
Please pull the following set of GPIO driver fixes for the upcoming RC.
Thanks,
Bartosz
The following changes since commit 5200f5f493f79f14bbdc349e402a40dfb32f23c8:
Linux 7.1-rc4 (2026-05-17 13:59:58 -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.1-rc5
for you to fetch changes up to a4fa45c1d980bc2b9837f469119af24a9304a1fc:
gpio: virtuser: lock device when calling device_is_bound() (2026-05-21 14:36:07 +0200)
----------------------------------------------------------------
gpio fixes for v7.1-rc5
- propagate the error code from regulator_enable() in resume path in
gpio-pca953x
- take the device lock when calling device_is_bound() in virtual GPIO
drivers
- fix software node leak in remove path in gpio-aggregator
- fix a potential use-after-free in gpio-aggregator
- harden the GPIO character device uAPI: check that line config
attributes are correctly zeroed
----------------------------------------------------------------
Bartosz Golaszewski (6):
gpio: cdev: check if uAPI v2 config attributes are correctly zeroed
gpio: aggregator: fix a potential use-after-free
gpio: aggregator: remove the software node when deactivating the aggregator
gpio: sim: lock device when calling device_is_bound()
gpio: aggregator: lock device when calling device_is_bound()
gpio: virtuser: lock device when calling device_is_bound()
Stepan Ionichev (1):
gpio: pca953x: propagate regulator_enable() error from resume
drivers/gpio/gpio-aggregator.c | 15 +++++++++++----
drivers/gpio/gpio-pca953x.c | 2 +-
drivers/gpio/gpio-sim.c | 11 +++++++----
drivers/gpio/gpio-virtuser.c | 9 ++++++---
drivers/gpio/gpiolib-cdev.c | 13 +++++++++++++
5 files changed, 38 insertions(+), 12 deletions(-)
next reply other threads:[~2026-05-22 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 9:36 Bartosz Golaszewski [this message]
2026-05-22 19:38 ` 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=20260522093622.24099-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®