[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151202181330.GG64635@google.com>
Date: Wed, 2 Dec 2015 10:13:30 -0800
From: Brian Norris <computersforpeace@...il.com>
To: Tony Lindgren <tony@...mide.com>
Cc: Roger Quadros <rogerq@...com>, dwmw2@...radead.org,
ezequiel@...guardiasur.com.ar, javier@...hile0.org, fcooper@...com,
nsekhar@...com, linux-mtd@...ts.infradead.org,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Boris Brezillon <boris.brezillon@...e-electrons.com>
Subject: Re: [PATCH v3 00/27] memory: omap-gpmc: mtd: nand: Support GPMC NAND
on non-OMAP platforms
On Wed, Dec 02, 2015 at 07:03:17AM -0800, Tony Lindgren wrote:
> * Roger Quadros <rogerq@...com> [151201 21:13]:
> > On 02/12/15 08:56, Brian Norris wrote:
> > >
> > > I'll take another pass over your patch set, but if things are looking
> > > better, how do you expect to merge this? There are significant portions
> > > that touch at least 2 or 3 different subsystem trees, AFAICT.
> >
> > Tony could create an immutable branch with all the dts and memory changes.
> > You could base the mtd changes on top of that?
>
> If we all agree on that it will be immutable Roger can set up the branch
> with our acks and we can all merge it in as needed. I believe v4.4-rc1
> should work as a base for us all?
There are oustanding comments about the NAND ready/busy GPIO naming in
patch 18, which I'd like addressed. I'll re-review the rest before the
end of the day (West Coast U.S.A.). I'm not sure my acks are worth much
beyond the MTD stuff.
Regarding branches, 4.4-rc1 is fine with me.
Regards,
Brian
--
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