From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Fabien Dessenne <fabien.dessenne@foss.st.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Last pin control fixes for v5.13
Date: Sat, 26 Jun 2021 01:34:01 +0200 [thread overview]
Message-ID: <CACRpkdaVqdFPKTxOuhFt=auFYjxCivRmRz7mQ7ank6rbcVQsQw@mail.gmail.com> (raw)
Hi Linus,
some last minute pin control fixes. A bit late because
I have some vacation and midsommar. Two driver fixes,
details in the signed tag.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit 009c9aa5be652675a06d5211e1640e02bbb1c33d:
Linux 5.13-rc6 (2021-06-13 14:43:10 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.13-3
for you to fetch changes up to 67e2996f72c71ebe4ac2fcbcf77e54479bb7aa11:
pinctrl: stm32: fix the reported number of GPIO lines per bank
(2021-06-18 14:56:54 +0200)
----------------------------------------------------------------
Two fixes in the last minute:
- Put an fwnode in the errorpath in the SGPIO driver
- Fix the number of GPIO lines per bank in the STM32 driver
----------------------------------------------------------------
Andy Shevchenko (1):
pinctrl: microchip-sgpio: Put fwnode in error case during ->probe()
Fabien Dessenne (1):
pinctrl: stm32: fix the reported number of GPIO lines per bank
drivers/pinctrl/pinctrl-microchip-sgpio.c | 4 +++-
drivers/pinctrl/stm32/pinctrl-stm32.c | 9 +++++++--
2 files changed, 10 insertions(+), 3 deletions(-)
next reply other threads:[~2021-06-25 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 23:34 Linus Walleij [this message]
2021-06-26 2:10 ` [GIT PULL] Last pin control fixes for v5.13 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='CACRpkdaVqdFPKTxOuhFt=auFYjxCivRmRz7mQ7ank6rbcVQsQw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=fabien.dessenne@foss.st.com \
--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).