From: Roland Dreier <rolandd@cisco.com>
To: mporter@kernel.crashing.org
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 2/4] [PPC32] Add 440SPe support
Date: Thu, 22 Sep 2005 22:44:35 -0700 [thread overview]
Message-ID: <52y85obanw.fsf@cisco.com> (raw)
In-Reply-To: 20050923032949.GB10089@gate.ebshome.net
Eugene> Roland, I recently added new field (.dcr_base) to this
Eugene> structure (as a preparation step for new EMAC driver),
Eugene> could you do this for 440SPe as well? It's not needed
Eugene> right now, but as soon as new EMAC driver is in, 440SPe
Eugene> will stop working.
Eugene> I think you probably missed this part :)
Both fixed and pushed in a new git tree...
- R.
next prev parent reply other threads:[~2005-09-23 5:44 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
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 [this message]
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=52y85obanw.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mporter@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.