From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: netdev@vger.kernel.org, jeff@garzik.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3 v2] ibm_newemac: Various fixes and additions for PPC405EZ
Date: Wed, 10 Sep 2008 23:21:03 -0400 [thread overview]
Message-ID: <20080910232103.15a9b87e@zod.rchland.ibm.com> (raw)
In-Reply-To: <cover.1220877899.git.jwboyer@linux.vnet.ibm.com>
On Mon, 8 Sep 2008 08:44:59 -0400
Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> The following patch series adds things needed to support the PowerPC 405EZ
> SoC. I've incorporated the suggestions and fixes from the previous round
> of patches and barring any further comments these should be ready to go.
>
> josh
>
> Josh Boyer (3):
> ibm_newemac: Allow the "no flow control" EMAC feature to work
> ibm_newemac: Introduce mal_has_feature
> ibm_newemac: MAL support for PowerPC 405EZ
I should mention that I have a platform support patch series that
depends on these for working ethernet. I can bring this set in through
my tree at the same time if the patches look fine and Jeff acks that.
josh
prev parent reply other threads:[~2008-09-11 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 12:44 [PATCH 0/3 v2] ibm_newemac: Various fixes and additions for PPC405EZ Josh Boyer
2008-09-04 12:57 ` [PATCH 1/3] ibm_newemac: Allow the "no flow control" EMAC feature to work Josh Boyer
2008-09-13 19:40 ` Jeff Garzik
2008-09-04 14:03 ` [PATCH 2/3 v2] ibm_newemac: Introduce mal_has_feature Josh Boyer
2008-09-04 14:08 ` [PATCH 3/3 v2] ibm_newemac: MAL support for PowerPC 405EZ Josh Boyer
2008-09-09 7:11 ` [PATCH 0/3 v2] ibm_newemac: Various fixes and additions for PPC405EZ Benjamin Herrenschmidt
2008-09-09 10:30 ` Josh Boyer
2008-09-11 3:21 ` Josh Boyer [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=20080910232103.15a9b87e@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=jeff@garzik.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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).