From: Jon Loeliger <jdl@freescale.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: [RFC 0/3] MPC8544 DS Request for Comments
Date: Wed, 07 Mar 2007 15:14:09 -0600 [thread overview]
Message-ID: <1173302049.23776.181.camel@ld0161-tx32> (raw)
Folks,
This series of 3 patches form the basis for the
MPC8544 DS port. These are not a complete port
patch set, as there is still some resolution and
work needed on resolving some PCI and PCI-Express
similarities with 86xx on the event horizon.
In the meantime, I would appreciate any comments
and feedback on the basic port as it stands today.
I have not yet gone over these with a fine-tooth
Anton Blanchard, so there may be some rough spots
in here still. Feel free to nudge me with a Franklin.
Thanks,
jdl
reply other threads:[~2007-03-07 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1173302049.23776.181.camel@ld0161-tx32 \
--to=jdl@freescale.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