From: Grant Likely <grant.likely@secretlab.ca>
To: Luotao Fu <l.fu@pengutronix.de>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.33 -next tree
Date: Wed, 9 Dec 2009 06:40:11 -0700 [thread overview]
Message-ID: <fa686aa40912090540s1a06c063g10641e90501e8bc1@mail.gmail.com> (raw)
In-Reply-To: <4B1F6D3A.3030500@pengutronix.de>
On Wed, Dec 9, 2009 at 2:26 AM, Luotao Fu <l.fu@pengutronix.de> wrote:
> Hi Grant,
>
> Grant Likely wrote:
>> Hi Ben, Stephen.
>>
>> I just prepared my next branch for 2.6.33:
>> git://git.secretlab.ca/git/linux-2.6 next
>>
>
> Just for curiosity: I noticed that you keep so far the further patches for the
> dedicated spi controller on mpc5200 in the next-spi tree. Any plan when they
> will be merged to the -next tree? Like mentioned before, some of them are
> essential, without which the driver doesn't work (at least on my board)
I based the next-spi tree on my regular next tree (which was
convenient, but lead to it looking like I had inappropriate stuff in
my spi tree). Once Ben asks Linus to pull his tree it will all look
correct. I'll ask Linux to pull my next-spi tree directly after Ben's
tree is in.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-12-09 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 6:10 2.6.33 -next tree Grant Likely
2009-11-05 8:02 ` Stephen Rothwell
2009-11-05 8:08 ` Grant Likely
2009-11-05 8:13 ` Stephen Rothwell
2009-12-08 21:33 ` Grant Likely
2009-12-08 21:54 ` Grant Likely
2009-12-08 22:29 ` Benjamin Herrenschmidt
2009-12-08 22:45 ` Andrew Morton
2009-12-08 22:50 ` Grant Likely
2009-12-09 4:25 ` Olof Johansson
2009-12-09 4:29 ` Benjamin Herrenschmidt
2009-12-09 9:26 ` Luotao Fu
2009-12-09 13:40 ` 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=fa686aa40912090540s1a06c063g10641e90501e8bc1@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=l.fu@pengutronix.de \
--cc=linuxppc-dev@ozlabs.org \
/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).