From: Kumar Gala <kumar.gala@freescale.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Adrian Cox <adrian@humboldt.co.uk>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH] OCP for MP10x
Date: Tue, 29 Jun 2004 10:21:13 -0500 [thread overview]
Message-ID: <F5009B2E-C9DF-11D8-A76E-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1088516489.20324.12.camel@localhost>
Tom,
This patch looks good to me.
- kumar
On Jun 29, 2004, at 8:41 AM, Adrian Cox wrote:
> Attached is the latest version of my OCP patch for MPC107/8240/8245.
> This unifies some openpic setup code, and ensures that the OCP devices
> are only added to the bus on chip variants which have them.
> All interested parties seem happy, and this patch is necessary to
> provide a unified I2C driver for 85xx and 107/824x.
> Signed-off-by: Adrian Cox <adrian@humboldt.co.uk>
> - Adrian Cox
> Humboldt Solutions Ltd.
>
> <ocp3.patch>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-29 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 13:41 [PATCH] OCP for MP10x Adrian Cox
2004-06-29 15:21 ` Kumar Gala [this message]
2004-06-29 17:19 ` Tom Rini
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=F5009B2E-C9DF-11D8-A76E-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=adrian@humboldt.co.uk \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.