[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131009151015.GZ8313@atomide.com>
Date: Wed, 9 Oct 2013 08:10:15 -0700
From: Tony Lindgren <tony@...mide.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Grygorii Strashko <grygorii.strashko@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@...com>,
Prakash Manjunathappa <prakash.pm@...com>,
Haojian Zhuang <haojian.zhuang@...aro.org>,
Linux-OMAP <linux-omap@...r.kernel.org>,
Roger Quadros <rogerq@...com>
Subject: Re: [PATCH 3/6] pinctrl: single: Prepare for supporting SoC
specific features
* Linus Walleij <linus.walleij@...aro.org> [131009 06:51]:
> On Mon, Oct 7, 2013 at 7:35 PM, Tony Lindgren <tony@...mide.com> wrote:
>
> > Hi Linus W,
> >
> > Any comments on the pinctrl patches 3 - 5 in this series?
>
> Yes, after good explanations to my whimsical questions only this:
> Acked-by: Linus Walleij <linus.walleij@...aro.org>
OK thanks :)
> I guess you'll take these patches through ARM SoC?
I was thinking I'll set up an immutable branch for the three
pinctrl patches against -rc4 then both you and I can merge
them in as needed. Does that work for you?
I can also do a test merge with pinctrl/for-next also to make
sure there are no conflicts.
The rest of the patches should not be needed in the pinctrl
branch, but I need them all in one branch to keep things
working.
Regards,
Tony
--
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