[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF04B24A40D2@HQMAIL01.nvidia.com>
Date: Fri, 26 Aug 2011 09:07:00 -0700
From: Stephen Warren <swarren@...dia.com>
To: Olof Johansson <olof@...om.net>
CC: Grant Likely <grant.likely@...retlab.ca>,
Colin Cross <ccross@...roid.com>,
Erik Gilling <konkers@...roid.com>,
Russell King <linux@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Belisko Marek <marek.belisko@...il.com>,
Jamie Iles <jamie@...ieiles.com>,
Shawn Guo <shawn.guo@...escale.com>,
Sergei Shtylyov <sshtylyov@...sta.com>,
Linus Walleij <linus.walleij@...aro.org>
Subject: RE: [PATCH v3 00/13] arm/tegra: Initialize GPIO & pinmux from DT
Olof Johansson wrote at Thursday, August 25, 2011 11:05 PM:
> On Thu, Aug 25, 2011 at 4:43 PM, Stephen Warren <swarren@...dia.com> wrote:
> > v3:
...
> This is looking pretty sane to me.
>
> Grant, how do you prefer to handle this, since it spans of/dt, gpio
> and tegra code? I can start a topic branch for Arnd to pull in for the
> tegra parts, would you prefer picking up the of helper functions on
> your own or is an ack from you and merge through the arm-soc tree
> easier?
I haven't thought through all the merging details yet, but do be aware
of the dependencies this patchset has:
1) Rename of arch/arm/mach-tegra/gpio.c -> drivers/gpio/gpio-tegra.c
This is in Grant's gpio for-next branch, and hence linux-next.
This is in some GPIO-related branch of Russell's.
2) Various previous Tegra <mach/gpio.h> rework.
This is in some GPIO-related branch of Russell's; I assume the same one
as (1), but I can't actually find this branch, so can't check.
Neither of those is in any Linus release or rc.
I *think* that's it.
For reference, this patchset was physical written/tested on top of
next-20110823, with the patches mentioned in (2) aboe, and some others that
hopefully aren't relevant, between linux-next and this patchset.
--
nvpublic
--
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