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.0-rc4
Date: Fri, 13 Mar 2026 10:11:09 +0100 [thread overview]
Message-ID: <20260313091110.7691-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 11439c4635edd669ae435eec308f4ab8a0804808:
Linux 7.0-rc2 (2026-03-01 15:39:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v7.0-rc4
for you to fetch changes up to a23463beb3d52815e5f8e61998f5c94f13274544:
gpio: gpiolib: fix allocation order in hierarchical IRQ domains (2026-03-11 15:21:43 +0100)
----------------------------------------------------------------
gpio fixes for v7.0-rc4
- clear the "requested" flag in error path in GPIO core
- fix a NULL-pointer dereference in GPIO hierarchical IRQ handling
- driver kerneldoc fixes
----------------------------------------------------------------
Barnabás Pőcze (1):
gpiolib: clear requested flag if line is invalid
Oleksij Rempel (1):
gpio: gpiolib: fix allocation order in hierarchical IRQ domains
Randy Dunlap (2):
gpio: timberdale: repair kernel-doc comments
gpio: nomadik: repair some kernel-doc comments
drivers/gpio/gpiolib.c | 38 +++++++++++++++++++++-----------------
include/linux/gpio/gpio-nomadik.h | 12 +++++-------
include/linux/timb_gpio.h | 6 +++---
3 files changed, 29 insertions(+), 27 deletions(-)
next reply other threads:[~2026-03-13 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 9:11 Bartosz Golaszewski [this message]
2026-03-13 14:36 ` Bartosz Golaszewski
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=20260313091110.7691-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®