[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140224150521.GD14250@titan.lakedaemon.net>
Date: Mon, 24 Feb 2014 10:05:21 -0500
From: Jason Cooper <jason@...edaemon.net>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Gregory Clement <gregory.clement@...e-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 00/16] pinctrl: mvebu: restructure resource
allocation
On Mon, Feb 24, 2014 at 11:22:51AM +0100, Linus Walleij wrote:
> On Sun, Feb 23, 2014 at 4:40 PM, Jason Cooper <jason@...edaemon.net> wrote:
>
> > I certainly don't want to assume we can take this, and you've been quiet
> > on the previous versions of this series. We have a lot of moving pieces
> > for getting the Armada 375/380/385 support added to the kernel. It's a
> > huge help to us if we can create a topic branch for you with the pinctrl
> > changes in it.
>
> I understand, sorry I was on a short vacation.
What?! :) I was just the opposite. I've been laid up for five days
now after some minor surgery. Nothing to do all day but bang away on my
laptop... Which was actually perfect timing for the new SoCs and the
kirkwood migration.
> I've applied Thomas' two new SoC drivers and started queueing
> Sebastians series but it's a bit messy. Right now I'm not finding
> patch 06/21 v4....
>
> >> https://github.com/shesselba/linux-dove.git unstable/mvebu-pinctrl-v3.14_v4
>
> Should I just pull this in instead, as it contains both Thomas' and Sebastians
> patches, and then you can send me more stuff on top of that?
Please see my earlier reply to Thomas' 375/38x series. I have it all
set up for you and will send pull requests to you in a few days.
thx,
Jason.
--
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