From: Jeff Garzik <jeff@garzik.org>
To: Bryan Wu <bryan.wu@analog.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH 1/1] Blackfin EMAC driver: Fix Ethernet communication bug (dupliated and lost packets)
Date: Tue, 30 Oct 2007 14:32:41 -0400 [thread overview]
Message-ID: <472778C9.5040408@garzik.org> (raw)
In-Reply-To: <1193735049-7070-1-git-send-email-bryan.wu@analog.com>
Bryan Wu wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
>
> Fix Ethernet communication bug(dupliated and lost packets)
> in RMII PHY mode- dont call mac_disable and mac_enable during
> 10/100 REFCLK changes - mac_enable screws up the DMA descriptor chain
>
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> ---
> drivers/net/bfin_mac.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
applied
prev parent reply other threads:[~2007-10-30 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 9:04 [PATCH 1/1] Blackfin EMAC driver: Fix Ethernet communication bug (dupliated and lost packets) Bryan Wu
2007-10-30 18:32 ` Jeff Garzik [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=472778C9.5040408@garzik.org \
--to=jeff@garzik.org \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--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 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.