[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0708051926l63718982l4c991aebd817c94b@mail.gmail.com>
Date: Sun, 5 Aug 2007 22:26:10 -0400
From: "Mike Frysinger" <vapier.adi@...il.com>
To: bryan.wu@...log.com
Cc: "Linus Torvalds" <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
"David Brownell" <dbrownell@...rs.sourceforge.net>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] Blackfin arch update for 2.6.23
On 8/5/07, Bryan Wu <bryan.wu@...log.com> wrote:
> On Sun, 2007-08-05 at 22:04 -0400, Mike Frysinger wrote:
> > On 8/5/07, Bryan Wu <bryan.wu@...log.com> wrote:
> > > Bryan Wu (4):
> > > Blackfin SPI driver: Initial supporting BF54x in SPI driver
> > >
> > > Michael Hennerich (11):
> > > Blackfin arch: store labels so we later know who allocated GPIO/Peripheral resources
> > > Blackfin arch: add peripheral resource allocation support
> > > Blackfin arch: Add label to call new GPIO API
> > > Blackfin SPI driver: Make BF54x SPI work and add support for portmux API
> > > Blackfin SPI driver: use new GPIO API and add error handling
> >
> > i think this is the sort of thing Linus wants left for initial merge windows ?
> > -mike
>
> Actually, this GPIO API has been added to the upstream in -RC1. In this
> pull, Michael's patch just enable it in arch code and driver. And it is
> tested at least 2-3 weeks, I think it is OK for the -RC merge.
>
> And most our driver things are moved to depend on this new GPIO API. I
> just wanna make thing easier to maintain.
i was referring to the SPI stuff, not GPIO
-mike
-
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