From: "Mark A. Greer" <mgreer@mvista.com>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linuxppc-embedded@lists.linuxppc.org, kumar.gala@freescale.com
Subject: Re: [PATCH][RFC] Second version of MPC10x OCP
Date: Wed, 23 Jun 2004 11:51:19 -0700 [thread overview]
Message-ID: <40D9D127.4060303@mvista.com> (raw)
In-Reply-To: <1087746455.1547.23.camel@newt>
Adrian Cox wrote:
>Here's the second version of OCP-ifying the mpc10x. I've removed the
>hardcoded positions in the core_ocp array, and I've added the DMA
>devices in case anybody needs them. I haven't yet tested the I2C driver
>from 2.4, but I've put in the flags field for it.
>
>
Adrian,
Sorry for the delay, I've been out the last few days. FWIW, your patch
looks fine to me.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-23 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 15:47 [PATCH][RFC] Second version of MPC10x OCP Adrian Cox
2004-06-23 18:51 ` Mark A. Greer [this message]
2004-06-24 3:32 ` Kumar Gala
2004-06-24 16:36 ` Adrian Cox
2004-06-24 17:03 ` Kumar Gala
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=40D9D127.4060303@mvista.com \
--to=mgreer@mvista.com \
--cc=adrian@humboldt.co.uk \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-embedded@lists.linuxppc.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).