From: Jeff Garzik <jeff@garzik.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] ibm_newemac: Allow the "no flow control" EMAC feature to work
Date: Sat, 13 Sep 2008 15:40:55 -0400 [thread overview]
Message-ID: <48CC1747.40408@garzik.org> (raw)
In-Reply-To: <62e3d970a3bcb8158308bb645f99c75a41d177ff.1220877899.git.jwboyer@linux.vnet.ibm.com>
Josh Boyer wrote:
> Some PowerPC 40x chips have errata that force us not to use the integrated
> flow control. We have the feature defined, but it currently can't be used
> because it is never added to EMAC_FTRS_POSSIBLE.
>
> This adds a Kconfig option for affected platforms to select and puts the
> feature in the EMAC_FTRS_POSSIBLE list. This is set for PowerPC 405EZ
> platforms as well.
>
> Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
> ---
> drivers/net/ibm_newemac/Kconfig | 4 ++++
> drivers/net/ibm_newemac/core.c | 2 ++
> drivers/net/ibm_newemac/core.h | 3 +++
> 3 files changed, 9 insertions(+), 0 deletions(-)
ACK patches 1-3
next prev parent reply other threads:[~2008-09-13 19:41 UTC|newest]
Thread overview: 9+ 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 [this message]
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
[not found] <cover.1220540078.git.jwboyer@linux.vnet.ibm.com>
2008-09-04 15:01 ` [PATCH 1/3] ibm_newemac: Allow the "no flow control" EMAC feature to work 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=48CC1747.40408@garzik.org \
--to=jeff@garzik.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).