[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZ0kTXLAfdsfMjeZZX4W-fx5zyEdeGboKCmKSzCaMVw_A@mail.gmail.com>
Date: Fri, 10 Feb 2012 21:51:32 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Stephen Warren <swarren@...dia.com>
Cc: Olof Johansson <olof@...om.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Shawn Guo <shawn.guo@...escale.com>,
Thomas Abraham <thomas.abraham@...aro.org>,
Dong Aisheng <dong.aisheng@...aro.org>,
Rajendra Nayak <rajendra.nayak@...aro.org>,
Haojian Zhuang <haojian.zhuang@...vell.com>,
Barry Song <21cnbao@...il.com>,
Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH 0/3] pinctrl: move the core per-device handlers to core
On Fri, Feb 10, 2012 at 5:58 AM, Stephen Warren <swarren@...dia.com> wrote:
>> These three patches take the first step in this transformation by moving
>> the per-device handles over to core code, and renaming all related
>> functions with the pinctrl_* prefix.
>
> The series,
> Acked-by: Stephen Warren <swarren@...dia.com>
Thanks, I've managed to push this to -next with the v2 version of
[2/3] and the hog patch.
> Note that this series will cause some compile breakage in the series I
> previously posted to add a pinctrl-tegra driver and convert mach-tegra
> to use it. The following patches in that series should still be OK:
>
> pinctrl: add a driver for NVIDIA Tegra
> ARM: tegra: Select PINCTRL Kconfig variables
>
> ... so you can still go ahead and apply those, but the following will be
> broken:
>
> ARM: tegra: Switch to new pinctrl driver
> ARM: tegra: Remove pre-pinctrl pinmux driver
>
> also the separately posted:
>
> ARM: tegra: Add pinmux board file for Cardhu
>
> I'll probably hold off reposting those last 3; with any luck they'll be
> eclipsed by my implementing full DT binding support in the near future,
> given our consensus on that topic following discussion at Linaro Connect.
OK, alternatively I could remove these for the time being, or I
can fix up the mess I created if you prefer, by just adding
a patch on top, so it gets changed over no matter if the
DT stuff gets sorted out for this merge window?
Thanks,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists