From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: david-b@pacbell.net, Felix Radensky <felix@embedded-sol.com>
Subject: Re: 4xx tree updates
Date: Mon, 16 Feb 2009 09:30:07 +0100 [thread overview]
Message-ID: <200902160930.07203.sr@denx.de> (raw)
In-Reply-To: <20090215145854.GB30783@zod.rchland.ibm.com>
On Sunday 15 February 2009, Josh Boyer wrote:
> On Sun, Feb 15, 2009 at 05:31:40AM -0800, Felix Radensky wrote:
> >What about 4xx SPI driver ? Is it planned for inclusion in 2.6.30 ?
>
> I really hope so. I've Acked it twice now I think. However, that needs
> to go in through the SPI tree, which isn't mine.
I didn't receive any feedback on my lastest version (v6). So I'm guessing that
it's queued in David's patches for 2.6.30.
David, is this correct?
Best regards,
Stefan
prev parent reply other threads:[~2009-02-16 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 19:47 4xx tree updates Josh Boyer
2009-02-15 13:31 ` Felix Radensky
2009-02-15 14:58 ` Josh Boyer
2009-02-16 8:30 ` Stefan Roese [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=200902160930.07203.sr@denx.de \
--to=sr@denx.de \
--cc=david-b@pacbell.net \
--cc=felix@embedded-sol.com \
--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).