From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH net 0/2] net: systemport: RX path and suspend fixes
Date: Tue, 28 Oct 2014 11:11:59 -0700 [thread overview]
Message-ID: <1414519921-3246-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi David,
These two patches fix a race condition where we have our RX interrupts
enabled, but not NAPI for the RX path, and the second patch fixes an
issue for packets stuck in RX fifo during a suspend/resume cycle.
Thanks!
Florian Fainelli (2):
net: systemport: enable RX interrupts after NAPI
net: systemport: reset UniMAC coming out of a suspend cycle
drivers/net/ethernet/broadcom/bcmsysport.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
--
1.9.1
next reply other threads:[~2014-10-28 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 18:11 Florian Fainelli [this message]
2014-10-28 18:12 ` [PATCH net 1/2] net: systemport: enable RX interrupts after NAPI Florian Fainelli
2014-10-28 18:12 ` [PATCH net 2/2] net: systemport: reset UniMAC coming out of a suspend cycle Florian Fainelli
2014-10-28 21:11 ` [PATCH net 0/2] net: systemport: RX path and suspend fixes David Miller
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=1414519921-3246-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--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