[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdbL9DbJ7pMVabjOqw6HeWY5N-u7JmK3TdzQVvpZgy0RNg@mail.gmail.com>
Date: Thu, 16 Feb 2012 19:49:04 +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 Mon, Feb 13, 2012 at 9:01 PM, Stephen Warren <swarren@...dia.com> wrote:
> Linus Walleij wrote at Monday, February 13, 2012 12:48 PM:
>>
>> I'm mainly thinking if the underlying driver may be subject to change I
>> could just keep it out-of-tree, unless you want it merged in for some
>> practical reason, then I'll just merge it.
>
> IIRC, people hoped that the common pinctrl bindings would make it into
> 3.4. If that happens, the driver won't be unused in 3.4.
>
> I don't foresee any changes to the driver except those driven by any
> changes to the core pinctrl itself, so I don't foresee any need to keep
> it out of tree.
OK however since the patches no longer mess around in arch/arm/mach-*
I guess it's OK if I just throw it on the top of my patch queue with
everything else rather than as a separate branch?
I'll do that for now, tell me if it causes any problems!
Yours,
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