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] final pin control fixes for v5.12
Date: Sat, 24 Apr 2021 01:22:36 +0200 [thread overview]
Message-ID: <CACRpkdY6g7eoqyJ-OHijbR_Gw2W7uoNF5Z6+-at5OBvaH9_kqw@mail.gmail.com> (raw)
Hi Linus,
some late pin control fixes, would have been in the main pull request
normally but hey I got lucky and we got another week to polish up v5.12
so here we go.
One driver fix and one making the core debugfs work.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:
Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.12-3
for you to fetch changes up to 482715ff0601c836152b792f06c353464d826b9b:
pinctrl: core: Show pin numbers for the controllers with base = 0
(2021-04-22 02:13:42 +0200)
----------------------------------------------------------------
Late pin control fixes for v5.12:
- Fix the number of pins in the community of the Intel
Lewisburg SoC.
- Show pin numbers for controllers with base = 0 in the
new debugfs feature.
----------------------------------------------------------------
Andy Shevchenko (1):
pinctrl: core: Show pin numbers for the controllers with base = 0
Linus Walleij (1):
Merge tag 'intel-pinctrl-v5.12-4' of
gitolite.kernel.org:pub/scm/linux/kernel/git/pinctrl/intel into fixes
Yuanyuan Zhong (1):
pinctrl: lewisburg: Update number of pins in community
drivers/pinctrl/core.c | 14 ++++++++------
drivers/pinctrl/intel/pinctrl-lewisburg.c | 6 +++---
2 files changed, 11 insertions(+), 9 deletions(-)
next reply other threads:[~2021-04-23 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 23:22 Linus Walleij [this message]
2021-04-24 0:46 ` [GIT PULL] final pin control fixes for v5.12 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=CACRpkdY6g7eoqyJ-OHijbR_Gw2W7uoNF5Z6+-at5OBvaH9_kqw@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).