From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Boyan Ding <boyan.j.ding@gmail.com>
Subject: [GIT PULL] pin control fix for v5.5
Date: Sat, 25 Jan 2020 11:55:57 +0100 [thread overview]
Message-ID: <CACRpkdZ746gURHOeNf3Wj3_7BVHtxjd9Hz2n7QTmqxEroZ0N7A@mail.gmail.com> (raw)
Hi Linus,
here is a hopefully last pin control fix for the v5.5
series fixing up interrupts on the Sunrisepoint.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit b3a987b0264d3ddbb24293ebff10eddfc472f653:
Linux 5.5-rc6 (2020-01-12 16:55:08 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v5.5-5
for you to fetch changes up to 319d5cce728cd70897a1306591a252258fc1428d:
Merge tag 'intel-pinctrl-v5.5-3' of
git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel into fixes
(2020-01-17 09:07:26 +0100)
----------------------------------------------------------------
A single fix for the Intel Sunrisepoint pin controller
that makes the interrupts work properly on it.
----------------------------------------------------------------
Boyan Ding (1):
pinctrl: sunrisepoint: Add missing Interrupt Status register offset
Linus Walleij (1):
Merge tag 'intel-pinctrl-v5.5-3' of
git://git.kernel.org/.../pinctrl/intel into fixes
drivers/pinctrl/intel/pinctrl-sunrisepoint.c | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2020-01-25 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 10:55 Linus Walleij [this message]
2020-01-25 19:05 ` [GIT PULL] pin control fix for v5.5 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=CACRpkdZ746gURHOeNf3Wj3_7BVHtxjd9Hz2n7QTmqxEroZ0N7A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=boyan.j.ding@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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).