From: David Miller <davem@davemloft.net>
To: Xiaotian.Feng@windriver.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH net] gianfar: fix babbling rx error event bug
Date: Tue, 26 May 2009 20:48:15 -0700 (PDT) [thread overview]
Message-ID: <20090526.204815.185454308.davem@davemloft.net> (raw)
In-Reply-To: <1243389156-1668-1-git-send-email-Xiaotian.Feng@windriver.com>
From: Xiaotian Feng <Xiaotian.Feng@windriver.com>
Date: Wed, 27 May 2009 09:52:36 +0800
> Gianfar interrupt handler uses IEVENT_ERR_MASK to check and handle errors.
> Babbling RX error (IEVENT_BABR) should be included in IEVENT_ERROR_MASK.
> Otherwise if BABR is raised, it never gets handled nor cleared, and an
> interrupt storm results. This has been observed to happen on sending a
> burst of ethernet frames to a gianfar based board.
>
> Signed-off-by: Xiaotian Feng <xiaotian.feng@windriver.com>
Patch applied, thanks.
prev parent reply other threads:[~2009-05-27 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 1:52 [PATCH net] gianfar: fix babbling rx error event bug Xiaotian Feng
2009-05-27 3:48 ` David Miller [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=20090526.204815.185454308.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Xiaotian.Feng@windriver.com \
--cc=linux-kernel@vger.kernel.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).