From: David Brownell <david-b@pacbell.net>
To: "Mike Frysinger" <vapier.adi@gmail.com>, bryan.wu@analog.com
Cc: "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: Mon, 6 Aug 2007 09:07:02 -0700 [thread overview]
Message-ID: <200708060907.02506.david-b@pacbell.net> (raw)
In-Reply-To: <8bd0f97a0708051904n294d5955r4dd801ca6b38b5a8@mail.gmail.com>
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 ...
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.
- Dave
next prev parent reply other threads:[~2007-08-06 16:07 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 [this message]
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=200708060907.02506.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--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