From: Bryan Wu <bryan.wu@analog.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: bryan.wu@analog.com,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
David Brownell <dbrownell@users.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] Blackfin arch update for 2.6.23
Date: Mon, 06 Aug 2007 10:10:46 +0800 [thread overview]
Message-ID: <1186366246.5609.4.camel@roc-desktop> (raw)
In-Reply-To: <8bd0f97a0708051904n294d5955r4dd801ca6b38b5a8@mail.gmail.com>
On Sun, 2007-08-05 at 22:04 -0400, Mike Frysinger wrote:
> On 8/5/07, Bryan Wu <bryan.wu@analog.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.
Thanks Mike
- Bryan Wu
next prev parent reply other threads:[~2007-08-06 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 13:02 [GIT PULL] Blackfin arch update for 2.6.23 Bryan Wu
2007-08-06 2:04 ` Mike Frysinger
2007-08-06 2:10 ` Bryan Wu [this message]
2007-08-06 2:26 ` Mike Frysinger
2007-08-06 2:34 ` Bryan Wu
2007-08-06 16:07 ` David Brownell
2007-08-07 2:06 ` Bryan Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1186366246.5609.4.camel@roc-desktop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vapier.adi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox