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-rc1
Date: Fri, 24 Apr 2026 09:59:03 +0200 [thread overview]
Message-ID: <20260424075903.5997-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 1334d2a3b3235d062e5e1f51aebe7a64ed57cf72:
Merge tag 'gpio-updates-for-v7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux (2026-04-13 20:10: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-rc1
for you to fetch changes up to e31eee4a961077d60ef2362507240c6743c1c2ae:
gpio: aspeed: fix AST2700 debounce selector bit definitions (2026-04-20 11:10:39 +0200)
----------------------------------------------------------------
gpio fixes for v7.1-rc1
- fix a regression in gpio-rockchip introduced on older chips during the
merge window when converting to dynamic GPIO base
- fix AST2700 debounce selector bit definitions in gpio-aspeed
----------------------------------------------------------------
Billy Tsai (1):
gpio: aspeed: fix AST2700 debounce selector bit definitions
Jonas Karlman (1):
gpio: rockchip: Fix GPIO regression after conversion to dynamic base allocation
drivers/gpio/gpio-aspeed.c | 4 ++--
drivers/gpio/gpio-rockchip.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2026-04-24 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 7:59 Bartosz Golaszewski [this message]
2026-04-24 20:37 ` [GIT PULL] gpio fixes for v7.1-rc1 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=20260424075903.5997-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