From: Eugene Surovegin <ebs@ebshome.net>
To: Roland Dreier <rolandd@cisco.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 3/4] [PPC32] ibm_emac: Add 440SPe support
Date: Fri, 23 Sep 2005 01:24:07 -0700 [thread overview]
Message-ID: <20050923082407.GA14671@gate.ebshome.net> (raw)
In-Reply-To: <52irwscq49.fsf@cisco.com>
On Thu, Sep 22, 2005 at 10:25:26PM -0700, Roland Dreier wrote:
> No problem at all. Here's a patch against your git tree -- only
> tested on my Yucca board, so you might want to doublecheck that I
> didn't break all the systems will the opposite polarity.
Thanks Roland, I've just pushed your patch with minor style changes
to my GIT tree.
I changed uint32_t -> u32 and moved emac_phy_done() functions to
ibm_emac.h. Booted new kernel on Ocotea and everything seems to be OK.
--
Eugene
next prev parent reply other threads:[~2005-09-23 8:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 3:03 [PATCH 0/4] 440SPe support Roland Dreier
2005-09-23 3:03 ` [PATCH 1/4] [PPC32] Allow ERPN for early serial to depend on CPU type Roland Dreier
2005-09-23 3:03 ` [PATCH 2/4] [PPC32] Add 440SPe support Roland Dreier
2005-09-23 3:03 ` [PATCH 3/4] [PPC32] ibm_emac: " Roland Dreier
2005-09-23 3:03 ` [PATCH 4/4] [PPC32] Add Yucca (440SPe eval board) platform Roland Dreier
2005-09-23 3:32 ` Eugene Surovegin
2005-09-23 5:44 ` Roland Dreier
2005-09-23 3:22 ` [PATCH 3/4] [PPC32] ibm_emac: Add 440SPe support Eugene Surovegin
2005-09-23 5:25 ` Roland Dreier
2005-09-23 8:24 ` Eugene Surovegin [this message]
2005-09-23 15:17 ` Roland Dreier
2005-09-23 17:11 ` Matt Porter
2005-09-23 20:25 ` Roland Dreier
2005-09-23 20:36 ` Matt Porter
2005-09-23 3:29 ` [PATCH 2/4] [PPC32] " Eugene Surovegin
2005-09-23 5:44 ` Roland Dreier
2005-09-23 17:17 ` Matt Porter
2005-09-23 20:27 ` Roland Dreier
2005-09-23 17:20 ` Matt Porter
2005-09-23 20:27 ` Roland Dreier
2005-09-23 22:44 ` Roland Dreier
2005-09-23 22:58 ` Eugene Surovegin
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=20050923082407.GA14671@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rolandd@cisco.com \
/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).