[GIT PULL] Pin control fixes for the v4.4 series

[Linus Walleij]

Hi Linus,

here is a set of assorted pin control fixes for the v4.4 series.
More details in the signed tag as usual.

Please pull this in.

Yours,
Linus Walleij

The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:

  Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v4.4-2

for you to fetch changes up to 48111b79b77f9fb1f139e1878b3cfcd56b46b789:

  pinctrl: sh-pfc: sh7734: Add missing cfg macro parameter to fix
build (2015-12-01 11:13:04 +0100)

----------------------------------------------------------------
These are some v4.4 pin control fixes:

- Drop a redundant if-clause from Kconfig

- Fix a missing of_node_put() memory leak in the
  Freescale i.MX driver

- Fix 64bit compilation of the Qualcomm SSBI driver.

- Fix a logic inversion in the Mediatek driver.

- Fix a compilation error for the odd one off in the
  Super-H instance of the SH PFC driver.

----------------------------------------------------------------
Arnd Bergmann (1):
      pinctrl: fix qcom ssbi drivers for 64-bit compilation

Geert Uytterhoeven (1):
      pinctrl: sh-pfc: sh7734: Add missing cfg macro parameter to fix build

Hongzhou Yang (1):
      pinctrl: mediatek: Add get_direction support.

Masahiro Yamada (1):
      pinctrl: remove redundant if conditional from Kconfig

Vaishali Thakkar (1):
      pinctrl: imx1-core: add missing of_node_put

 drivers/pinctrl/Kconfig                       |  4 ----
 drivers/pinctrl/freescale/pinctrl-imx1-core.c |  8 ++++++--
 drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 11 ++++-------
 drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c      |  2 +-
 drivers/pinctrl/qcom/pinctrl-ssbi-mpp.c       |  2 +-
 drivers/pinctrl/sh-pfc/pfc-sh7734.c           |  6 +++---
 6 files changed, 15 insertions(+), 18 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/