From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: MPC85xx OCP->platform patches
Date: Wed, 17 Nov 2004 10:32:53 -0500 [thread overview]
Message-ID: <1100705908.14467.9.camel@jmcmullan> (raw)
In-Reply-To: <OFE0A40B56.8334E6F8-ONC1256F4E.002B5EF3@axxessit.no>
On Tue, 2004-11-16 at 09:06 +0100, miguel.valero@axxessit.no wrote:
> Probably, but the OCP or platform_device work is something that needs =
to
> get at some point. I'll take a look, if you're willing to push the
> driver with upstream I2C folks.
I have OCP->platform patches for 2.6.9 at
http://67.171.103.33/~gus/patches
They'll be moving to their permanent location at
http://www.evillabs.net/~gus/patches in a few hours.
These patches are currently being reviewed, so they may change at any
time without notice.
--=20
Jason McMullan <jason.mcmullan@timesys.com>
prev parent reply other threads:[~2004-11-17 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 8:06 MPC8260 I2C miguel.valero
2004-11-17 15:32 ` McMullan, Jason [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=1100705908.14467.9.camel@jmcmullan \
--to=jason.mcmullan@timesys.com \
--cc=linuxppc-embedded@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).