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>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Antonio Borneo <antonio.borneo@foss.st.com>
Subject: [GIT PULL] late pin control fixes for the v6.8 kernel
Date: Fri, 8 Mar 2024 15:04:32 +0100 [thread overview]
Message-ID: <CACRpkdYomV_hSse7tExpQXzuOarC35cqAJoSQPwwwbN0mi81yQ@mail.gmail.com> (raw)
Hi Linus,
here are some two late fixes for pin control.
Details in the signed tag.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:
Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v6.8-3
for you to fetch changes up to f6443e0177a55f78e94ccc1a43eb63a023a0b6fd:
pinctrl: don't put the reference to GPIO device in
pinctrl_pins_show() (2024-02-29 14:36:40 +0100)
----------------------------------------------------------------
Two pin control fixes for the v6.8 kernel series:
- Fix the PM suspend callback in the STM32 ST32MP257 driver to
properly support suspend.
- Drop an extraneous reference put in the debugfs code, this was
confusing the reference counts and causing unsolicited calls
to __free().
----------------------------------------------------------------
Antonio Borneo (1):
pinctrl: stm32: fix PM support for stm32mp257
Bartosz Golaszewski (1):
pinctrl: don't put the reference to GPIO device in pinctrl_pins_show()
drivers/pinctrl/core.c | 2 +-
drivers/pinctrl/stm32/pinctrl-stm32mp257.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2024-03-08 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 14:04 Linus Walleij [this message]
2024-03-08 22:28 ` [GIT PULL] late pin control fixes for the v6.8 kernel 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=CACRpkdYomV_hSse7tExpQXzuOarC35cqAJoSQPwwwbN0mi81yQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=antonio.borneo@foss.st.com \
--cc=brgl@bgdev.pl \
--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).