From: Matt Porter <mporter@kernel.crashing.org>
To: Roland Dreier <rolandd@cisco.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 2/4] [PPC32] Add 440SPe support
Date: Fri, 23 Sep 2005 10:17:12 -0700 [thread overview]
Message-ID: <20050923101712.F21055@cox.net> (raw)
In-Reply-To: <52y85obanw.fsf@cisco.com>; from rolandd@cisco.com on Thu, Sep 22, 2005 at 10:44:35PM -0700
On Thu, Sep 22, 2005 at 10:44:35PM -0700, Roland Dreier wrote:
> 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...
Can you rebase off of Eugene's tree and resend patches? For the moment
the new EMAC driver is the lynchpin in anything new PPC4xx. I want
to hold off merging anything that involves current EMAC driver changes
until the new driver is in. In any case, nothing like this can go upstream
until after 2.6.14 is released. We are expecting the new EMAC driver to
be merged at that point. If you have this stuff rebased from his tree
we can easily merge them post-EMAC merge.
-Matt
next prev parent reply other threads:[~2005-09-23 17:17 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
2005-09-23 17:17 ` Matt Porter [this message]
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=20050923101712.F21055@cox.net \
--to=mporter@kernel.crashing.org \
--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).