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>,
Phil Reid <preid@electromag.com.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Nicolas Boichat <drinkcat@chromium.org>
Subject: [GIT PULL] pin control fixes for v5.2
Date: Fri, 28 Jun 2019 10:35:45 +0100 [thread overview]
Message-ID: <CACRpkdaiMrQyaxrLhy=Az5SCoz_C3NWRSYiQFqr=_BsD+qugMQ@mail.gmail.com> (raw)
Hi Linus,
sorry to bomb in fixes this late. Maybe I can comfort you
by saying it is only driver fixes, and mostly IRQ handling
which is something GPIO and pin control drivers never get
right. You think it works and then it doesn't.
It also took some time because we smoked out commit
message syntax issues in linux-next.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:
Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.2-3
for you to fetch changes up to 9d957a959bc8c3dfe37572ac8e99affb5a885965:
pinctrl: mediatek: Update cur_mask in mask/mask ops (2019-06-27
12:22:11 +0100)
----------------------------------------------------------------
Pin control fixes for the v5.2 cycle:
- Fix IRQ setup in the MCP23s08.
- Fix pin setup on pins > 31 in the Ocelot driver.
- Fix IRQs in the Mediatek driver.
----------------------------------------------------------------
Alexandre Belloni (2):
pinctrl: ocelot: fix gpio direction for pins after 31
pinctrl: ocelot: fix pinmuxing for pins after 31
Nicolas Boichat (2):
pinctrl: mediatek: Ignore interrupts that are wake only during resume
pinctrl: mediatek: Update cur_mask in mask/mask ops
Phil Reid (1):
pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order
drivers/pinctrl/mediatek/mtk-eint.c | 34 +++++++++++++++++++---------------
drivers/pinctrl/pinctrl-mcp23s08.c | 8 ++++----
drivers/pinctrl/pinctrl-ocelot.c | 18 ++++++++++--------
3 files changed, 33 insertions(+), 27 deletions(-)
next reply other threads:[~2019-06-28 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 9:35 Linus Walleij [this message]
2019-06-29 9:30 ` [GIT PULL] pin control fixes for v5.2 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-05-28 8:43 Linus Walleij
2019-05-28 16:44 ` Linus Torvalds
2019-05-28 16:55 ` Randy Dunlap
2019-05-29 6:25 ` Linus Walleij
2019-05-28 16:50 ` 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='CACRpkdaiMrQyaxrLhy=Az5SCoz_C3NWRSYiQFqr=_BsD+qugMQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=drinkcat@chromium.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preid@electromag.com.au \
--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).