[GIT PULL] pin control fixes for the v3.11 series

From: Linus Walleij
Date: Sun Jul 28 2013 - 19:34:04 EST


Hi Linus,

these are some accumulated pin control changes for
the v3.11 series. It's been pretty calm in this tree post
the merge window this time.

Please pull them in!

Yours,
Linus Walleij


The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:

Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-for-v3.11-2

for you to fetch changes up to db6c2c69c27f2c4fd1e2a1c6b0b1119b1e885f8a:

pinctrl: fix a memleak when freeing maps (2013-07-25 17:18:36 +0200)

----------------------------------------------------------------
Pin control fixes for the v3.11 series:

- Driver fixes for AM33xx, SIRF and PFC pin controllers.

- Fix a compile warning from the pinctrl single-register
driver.

- Fix a little nasty memory leak.

----------------------------------------------------------------
Barry Song (1):
arm/dts: sirf: fix the pingroup name mismatch between drivers and dts

Guennadi Liakhovetski (1):
pinctrl: sh-pfc: fix SDHI0 VccQ regulator on sh73a0 with DT

Ian Campbell (1):
pinctrl: am33xx dt binding: correct include path

Jean-Francois Moine (1):
pinctrl: pinctrl-single: fix compile warning when no CONFIG_PM

Linus Walleij (1):
pinctrl: fix a memleak when freeing maps

Qipan Li (2):
pinctrl: sirf: fix the pin number and mux bit for usp0
pinctrl: sirf: add usp0_uart_nostreamctrl pin group for usp-uart
without flowctrl

arch/arm/boot/dts/atlas6.dtsi | 22 ++++++++++++++--------
arch/arm/boot/dts/prima2.dtsi | 16 ++++++++--------
drivers/pinctrl/core.c | 1 +
drivers/pinctrl/pinctrl-single.c | 2 ++
drivers/pinctrl/sh-pfc/pfc-sh73a0.c | 1 +
drivers/pinctrl/sirf/pinctrl-atlas6.c | 24 ++++++++++++++++++++++--
include/dt-bindings/pinctrl/am33xx.h | 2 +-
7 files changed, 49 insertions(+), 19 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/