From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: fixes for v6.9-rc6
Date: Fri, 26 Apr 2024 19:40:58 +0200 [thread overview]
Message-ID: <20240426174058.28301-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Please pull the following set of fixes for the next RC.
Thanks!
Bartosz
The following changes since commit ed30a4a51bb196781c8058073ea720133a65596f:
Linux 6.9-rc5 (2024-04-21 12:35:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio-fixes-for-v6.9-rc6
for you to fetch changes up to c714fcdf5b75f63ab27cb5071747194e5ada2433:
Merge tag 'intel-gpio-v6.9-2' of git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel into gpio/for-current (2024-04-25 14:35:55 +0200)
----------------------------------------------------------------
gpio fixes for v6.9-rc6
- fix a regression in pin access control in gpio-tegra186
- make data pointer dereference robust in Intel Tangier driver
----------------------------------------------------------------
Andy Shevchenko (1):
gpio: tangier: Use correct type for the IRQ chip data
Bartosz Golaszewski (1):
Merge tag 'intel-gpio-v6.9-2' of git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel into gpio/for-current
Prathamesh Shete (1):
gpio: tegra186: Fix tegra186_gpio_is_accessible() check
drivers/gpio/gpio-tangier.c | 9 ++++++---
drivers/gpio/gpio-tegra186.c | 20 +++++++++++---------
2 files changed, 17 insertions(+), 12 deletions(-)
next reply other threads:[~2024-04-26 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 17:40 Bartosz Golaszewski [this message]
2024-04-26 18:31 ` [GIT PULL] gpio: fixes for v6.9-rc6 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=20240426174058.28301-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).