From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Jeffery <andrew@aj.id.au>
Subject: [GIT PULL] last pin control fix for v5.3
Date: Thu, 12 Sep 2019 09:28:57 +0100 [thread overview]
Message-ID: <CACRpkdaF8PNXBR2+d7OBWmR7wqRy=iP3OOCJDAFV0rf_e5PaZQ@mail.gmail.com> (raw)
Hi Linus,
here is a hopefully last pin control fix for the Aspeed.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit d45331b00ddb179e291766617259261c112db872:
Linux 5.3-rc4 (2019-08-11 13:26:41 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.3-3
for you to fetch changes up to c1432423a16825ef94e019808ed7330ee33ffc69:
pinctrl: aspeed: Fix spurious mux failures on the AST2500
(2019-09-12 00:08:27 +0100)
----------------------------------------------------------------
Pin control fixes for v5.3:
- A single patch for some Aspeed problems. The BMCs are much
happier now.
----------------------------------------------------------------
Andrew Jeffery (1):
pinctrl: aspeed: Fix spurious mux failures on the AST2500
drivers/pinctrl/aspeed/pinctrl-aspeed-g5.c | 30 +++++++++++++++++++++++++++++-
drivers/pinctrl/aspeed/pinmux-aspeed.c | 7 +++++--
drivers/pinctrl/aspeed/pinmux-aspeed.h | 7 ++++---
3 files changed, 38 insertions(+), 6 deletions(-)
next reply other threads:[~2019-09-12 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 8:28 Linus Walleij [this message]
2019-09-12 10:15 ` [GIT PULL] last pin control fix for v5.3 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='CACRpkdaF8PNXBR2+d7OBWmR7wqRy=iP3OOCJDAFV0rf_e5PaZQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andrew@aj.id.au \
--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).