From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3 v2] ibm_newemac: Various fixes and additions for PPC405EZ
Date: Tue, 09 Sep 2008 17:11:23 +1000 [thread overview]
Message-ID: <1220944283.4879.323.camel@pasglop> (raw)
In-Reply-To: <cover.1220877899.git.jwboyer@linux.vnet.ibm.com>
On Mon, 2008-09-08 at 08:44 -0400, Josh Boyer 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.
For some reason, I got this email but not the 3 following patch ones...
Cheers,
Ben.
> 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
>
> arch/powerpc/include/asm/dcr-regs.h | 7 ++++
> drivers/net/ibm_newemac/Kconfig | 12 +++++++
> drivers/net/ibm_newemac/core.c | 2 +
> drivers/net/ibm_newemac/core.h | 3 ++
> drivers/net/ibm_newemac/mal.c | 60 ++++++++++++++++++++++++++++++++---
> drivers/net/ibm_newemac/mal.h | 34 ++++++++++++++++++++
> 6 files changed, 113 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2008-09-09 7:19 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 ` Benjamin Herrenschmidt [this message]
2008-09-09 10:30 ` [PATCH 0/3 v2] ibm_newemac: Various fixes and additions for PPC405EZ Josh Boyer
2008-09-11 3:21 ` Josh Boyer
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=1220944283.4879.323.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--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).