mbox series

[GIT,PULL] intel-pinctrl fixes for v5.4

Message ID 20191008110737.GE2819@lahna.fi.intel.com
State New
Headers show
Series [GIT,PULL] intel-pinctrl fixes for v5.4 | expand

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-fixes-v5.4

Message

Mika Westerberg Oct. 8, 2019, 11:07 a.m. UTC
Hi Linus,

The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:

  Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-fixes-v5.4

for you to fetch changes up to 260996c30f4f3a732f45045e3e0efe27017615e4:

  pinctrl: cherryview: restore Strago DMI workaround for all versions (2019-10-01 17:36:40 +0300)

----------------------------------------------------------------
intel-pinctrl fixes for v5.4

This includes two fixes for Intel pinctrl drivers:

  - Fix warning about shared irqchip
  - Restore Strago DMI workaround for all versions

----------------------------------------------------------------
Andy Shevchenko (1):
      pinctrl: intel: Allocate IRQ chip dynamic

Dmitry Torokhov (1):
      pinctrl: cherryview: restore Strago DMI workaround for all versions

 drivers/pinctrl/intel/pinctrl-cherryview.c |  4 ----
 drivers/pinctrl/intel/pinctrl-intel.c      | 27 ++++++++++++++-------------
 2 files changed, 14 insertions(+), 17 deletions(-)

Comments

Linus Walleij Oct. 10, 2019, 11:23 p.m. UTC | #1
On Tue, Oct 8, 2019 at 1:07 PM Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:

> The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
>
>   Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-fixes-v5.4
>
> for you to fetch changes up to 260996c30f4f3a732f45045e3e0efe27017615e4:
>
>   pinctrl: cherryview: restore Strago DMI workaround for all versions (2019-10-01 17:36:40 +0300)

Pulled in for fixes.

Thanks for all help!

Yours,
Linus Walleij