From: Grant Likely <grant.likely@secretlab.ca>
To: David Brownell <david-b@pacbell.net>
Cc: spi-devel-general@lists.sourceforge.net,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3 0/4 REPOST] OF infrastructure for SPI devices
Date: Mon, 28 Jul 2008 10:39:56 -0600 [thread overview]
Message-ID: <20080728163956.GC21039@secretlab.ca> (raw)
In-Reply-To: <200807271449.28472.david-b@pacbell.net>
On Sun, Jul 27, 2008 at 02:49:28PM -0700, David Brownell wrote:
> On Friday 25 July 2008, Grant Likely wrote:
> > I don't know what to do with these patches. I'd really like to see them
> > in .27, and now that akpm has cleared his queue, the prerequisite patch
> > has been merged so they are ready to go in. However, even though there
> > has been favourable reception on the SPI and linuxppc lists for these
> > changes I don't have any acks from anybody yet.
> >
> > David, can you please reply on if you are okay with these patches
> > getting merged? If so, do you want me to merge them via my tree, or
> > do you want to pick them up?
>
> OK ... to recap, #1 and #3 are OF-specific, I'll be agnostic.
> If other OF folk think it's OK, great.
>
> Some cleanup was needed for #2, but it was basically ok ...
> I'd like to see the final version, and if it goes via an
> OF push that's OK by me. (Though I'd like to see that change
> make it into 2.6.27 regardless, so let me know.)
Thanks for the review. 1-3 is already merged into my git tree and Ben
has pulled them. I hope that's okay. Here's a link to the commit:
http://git.kernel.org/?p=linux/kernel/git/benh/powerpc.git;a=commitdiff;h=dc87c98e8f635a718f1abb2c3e15fc77c0001651
Let me know if you see anything else that needs to be changed and I'll
submit a fixup patch.
> And #4 isn't quite cooked yet.
Okay, I'll hack on this more and post v4.
Thanks again,
g.
prev parent reply other threads:[~2008-07-28 16:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 7:33 [PATCH v3 0/4 REPOST] OF infrastructure for SPI devices Grant Likely
2008-07-25 7:33 ` [PATCH v3 1/4] of: adapt of_find_i2c_driver() to be usable by SPI also Grant Likely
2008-07-25 15:40 ` Jon Smirl
2008-07-25 16:21 ` Grant Likely
2008-07-25 17:02 ` Jon Smirl
2008-07-25 18:52 ` Grant Likely
2008-07-25 7:33 ` [PATCH v3 2/4] spi: split up spi_new_device() to allow two stage registration Grant Likely
2008-07-25 19:00 ` David Brownell
2008-07-25 19:34 ` Grant Likely
2008-07-25 7:33 ` [PATCH v3 3/4] spi: Add OF binding support for SPI busses Grant Likely
2008-07-25 7:33 ` [PATCH v3 4/4] powerpc/mpc5200: Add mpc5200-spi (non-PSC) device driver Grant Likely
2008-07-25 18:19 ` Daniel Walker
2008-07-26 2:45 ` Grant Likely
2008-07-26 4:47 ` Daniel Walker
2008-07-26 5:20 ` Grant Likely
2008-07-27 21:41 ` David Brownell
2008-07-25 14:46 ` [PATCH v3 0/4 REPOST] OF infrastructure for SPI devices Jon Smirl
2008-08-02 22:46 ` Jon Smirl
2008-07-27 21:49 ` David Brownell
2008-07-28 16:39 ` Grant Likely [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=20080728163956.GC21039@secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).