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
Date: Thu, 11 Jun 2026 09:42:57 +0200 [thread overview]
Message-ID: <20260611074257.5012-1-bartosz.golaszewski@oss.qualcomm.com> (raw)
Linus,
Please pull the final round of GPIO fixes for this release. They come in pretty
late but are all tiny and mostly in individual drivers.
Thanks,
Bartosz
The following changes since commit 4549871118cf616eecdd2d939f78e3b9e1dddc48:
Linux 7.1-rc7 (2026-06-07 15:37: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
for you to fetch changes up to a23226b7c1f69eafd9ced4e037fb51c9758c0501:
gpiolib: handle gpio-hogs only once (2026-06-10 10:12:57 +0200)
----------------------------------------------------------------
gpio fixes for v7.1
- fix NULL pointer dereference in gpio-mvebu
- fix runtime PM leak in remove path in gpio-zynq
- reject invalid module params in gpio-mockup
- fix generic IRQ chip leak in remove parh in gpio-rockchip
- fix resource leaks in GPIO chip cleanup path on hog failure
- fix a regression in how GPIO hogging code handles multiple GPIO chips
reusing the same OF node
----------------------------------------------------------------
Bartosz Golaszewski (1):
gpio: fix cleanup path on hog failure
Daniel Drake (1):
gpiolib: handle gpio-hogs only once
Marco Scardovi (1):
gpio: rockchip: fix generic IRQ chip leak on remove
Ruoyu Wang (1):
gpio: zynq: fix runtime PM leak on remove
Samuel Moelius (1):
gpio: mockup: reject invalid gpio_mockup_ranges widths
Yun Zhou (1):
gpio: mvebu: fix NULL pointer dereference in suspend/resume
drivers/gpio/gpio-mockup.c | 16 ++++++++++++++--
drivers/gpio/gpio-mvebu.c | 4 ++--
drivers/gpio/gpio-rockchip.c | 4 +++-
drivers/gpio/gpio-zynq.c | 1 +
drivers/gpio/gpiolib-of.c | 5 -----
drivers/gpio/gpiolib.c | 10 +++++++++-
6 files changed, 29 insertions(+), 11 deletions(-)
next reply other threads:[~2026-06-11 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 7:42 Bartosz Golaszewski [this message]
2026-06-11 20:58 ` 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=20260611074257.5012-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®