From: Tom Rini <trini@kernel.crashing.org>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] 8272ADS FCC clock setting
Date: Thu, 13 Jan 2005 07:57:47 -0700 [thread overview]
Message-ID: <20050113145747.GY3391@smtp.west.cox.net> (raw)
In-Reply-To: <9FCDBA58F226D911B202000BDBAD46730813D2@zch01exm40.ap.freescale.net>
On Thu, Jan 13, 2005 at 05:49:25PM +0800, Li Yang-r58472 wrote:
> The patches fix Clock pin Configuration of MPC8272ADS board FCC support, and clear up comment on it.
This shouldn't be required in linuxppc-2.4, as I pushed your patch to
cleanup the pin selection earlier, and I'll see about getting it into
2.4.30 (too late for 2.4.29). For 2.6, I've pushed these changes (along
with some others for PQ2FADS) into linuxppc-2.5, as the fcc_enet driver
in stock 2.6 needs massive updates (I'm hoping it can be obsoleted by a
new one from Andy Flemming).
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2005-01-13 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 9:49 [PATCH] 8272ADS FCC clock setting Li Yang-r58472
2005-01-13 14:57 ` Tom Rini [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=20050113145747.GY3391@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=LeoLi@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;
as well as URLs for NNTP newsgroup(s).