From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: [GIT PULL] pin control fixes for v5.16
Date: Sun, 26 Dec 2021 04:15:32 +0100 [thread overview]
Message-ID: <CACRpkdaJMVS5vmw5KweS8c1ptz+OoEguifdqRFP4mzU_chH8-w@mail.gmail.com> (raw)
Hi Linus,
here are some hopefully final pin control fixes for the
v5.16 kernel series.
Please pull it in!
God Jul och Gott Nytt År
Linus Walleij
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.16-3
for you to fetch changes up to b67210cc217f9ca1c576909454d846970c13dfd4:
pinctrl: stm32: consider the GPIO offset to expose all the GPIO
lines (2021-12-16 04:14:56 +0100)
----------------------------------------------------------------
Some hopefully final pin control fixes for the v5.16 kernel:
- Fix an out-of-bounds bug in the Mediatek driver
- Fix an init order bug in the Broadcom BCM2835 driver
- Fix a GPIO offset bug in the STM32 driver
----------------------------------------------------------------
Fabien Dessenne (1):
pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
Guodong Liu (1):
pinctrl: mediatek: fix global-out-of-bounds issue
Phil Elwell (1):
pinctrl: bcm2835: Change init order for gpio hogs
drivers/pinctrl/bcm/pinctrl-bcm2835.c | 29 +++++++++++++-----------
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 8 +++++--
drivers/pinctrl/stm32/pinctrl-stm32.c | 8 +++----
3 files changed, 26 insertions(+), 19 deletions(-)
next reply other threads:[~2021-12-26 3:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 3:15 Linus Walleij [this message]
2021-12-26 4:02 ` [GIT PULL] pin control fixes for v5.16 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2021-11-20 2:26 Linus Walleij
2021-11-20 19:20 ` 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=CACRpkdaJMVS5vmw5KweS8c1ptz+OoEguifdqRFP4mzU_chH8-w@mail.gmail.com \
--to=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).