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
Date: Fri, 10 Apr 2026 10:42:10 +0200 [thread overview]
Message-ID: <20260410084210.14239-1-bartosz.golaszewski@oss.qualcomm.com> (raw)
Linus,
Please pull the following set of tiny GPIO driver fixes for v7.0. This is
the final GPIO PR for this release.
Thanks,
Bartosz
The following changes since commit 591cd656a1bf5ea94a222af5ef2ee76df029c1d2:
Linux 7.0-rc7 (2026-04-05 15:26:23 -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.0
for you to fetch changes up to 57df6923ca53b524d06d2347b896d9de74b3bc86:
gpio: tegra: return -ENOMEM on allocation failure in probe (2026-04-10 09:01:24 +0200)
----------------------------------------------------------------
gpio fixes for v7.0
- gracefully handle missing regmap in gpio-bd72720
- fix IRQ resource release in gpio-tegra
- return -ENOMEM on devm_kzalloc() failure instead of -ENODEV in
gpio-tegra
----------------------------------------------------------------
Matti Vaittinen (1):
gpio: bd72720: handle missing regmap
Samasth Norway Ananda (2):
gpio: tegra: fix irq_release_resources calling enable instead of disable
gpio: tegra: return -ENOMEM on allocation failure in probe
drivers/gpio/gpio-bd72720.c | 2 ++
drivers/gpio/gpio-tegra.c | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2026-04-10 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 8:42 Bartosz Golaszewski [this message]
2026-04-10 16:45 ` 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=20260410084210.14239-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®