From: Bryan Wu <bryan.wu@analog.com>
To: David Brownell <david-b@pacbell.net>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
bryan.wu@analog.com,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] Blackfin arch update for 2.6.23
Date: Tue, 07 Aug 2007 10:06:38 +0800 [thread overview]
Message-ID: <1186452398.6413.13.camel@roc-laptop> (raw)
In-Reply-To: <200708060907.02506.david-b@pacbell.net>
On Mon, 2007-08-06 at 09:07 -0700, David Brownell wrote:
> On Sunday 05 August 2007, 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 ?
>
> What, merging patches that have never even been seen by the relevant
> subsystem maintainer(s)?
>
> I've never seen any of those SPI patches before, and am not inclined
> to try plucking three of them out of a composite patch for a separate
> review ...
>
Yeah, although the Blackfin on-chip SPI driver is originally developed
by Luke Yang, currently it is maintained by me. Sorry for this missing,
I will send driver update patches
to related subsystem maintainers in LKML.
> Same goes for GPIO, for that matter. It's harder to goof those up,
> but it's still possible. If those were reviewed I personally might
> be inclined to OK merges after RC1; GPIOs get used almost everywhere.
> (Pretty much as Bryan commented...) Those look more like portmux
> changes than GPIO changes though.
Actually, I wanna to obey the merge window policy, but there are some
many changes in my local tree related to GPIO, silicon anomaly (common
fixing). So I choose GPIO changes in this git-pull, thanks for your
understanding situation.
I will remove the SPI driver patch from this GIT-PULL, a new GIT-PULL
will be requested.
(Frankly speaking, I am afraid of being added to Linus's shit-list for
the next few releases, -:(( ).
Thanks a lot, Mike and David.
Best Regards,
- Bryan Wu
prev parent reply other threads:[~2007-08-07 2:08 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
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 [this message]
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=1186452398.6413.13.camel@roc-laptop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.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