From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] pin control fixes for v4.12, take three
Date: Tue, 20 Jun 2017 13:51:23 +0200 [thread overview]
Message-ID: <CACRpkdY-vFyd1F8SysCdpTRAr0bf63H1m6JBikfzv454dYyi5w@mail.gmail.com> (raw)
Hi Linus,
some late arriving fixes. I should have sent earlier, just swamped
with work as usual. Thomas patch makes AMD systems usable
despite driver bugs so it is fairly important.
Please pull in these two patches!
Yours,
Linus Walleij
The following changes since commit 3c2993b8c6143d8a5793746a54eba8f86f95240f:
Linux 4.12-rc4 (2017-06-04 16:47:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v4.12-3
for you to fetch changes up to b7c747d4627462f25b3daabf49c18895a6722faa:
pinctrl: stm32: Fix bad function call (2017-06-09 10:51:54 +0200)
----------------------------------------------------------------
Pin control fixes for v4.12, take three:
- Make the AMD driver use a regular interrupt rather than a chained one,
so the system does not lock up.
- Fix a function call error deep inside the STM32 driver.
----------------------------------------------------------------
Alexandre TORGUE (1):
pinctrl: stm32: Fix bad function call
Thomas Gleixner (1):
pinctrl/amd: Use regular interrupt instead of chained
drivers/pinctrl/pinctrl-amd.c | 91 ++++++++++++++++-------------------
drivers/pinctrl/stm32/pinctrl-stm32.c | 2 +-
2 files changed, 42 insertions(+), 51 deletions(-)
next reply other threads:[~2017-06-20 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 11:51 Linus Walleij [this message]
2017-06-20 12:24 ` [GIT PULL] pin control fixes for v4.12, take three Thomas Gleixner
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=CACRpkdY-vFyd1F8SysCdpTRAr0bf63H1m6JBikfzv454dYyi5w@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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).