From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/4] be2net fixes
Date: Fri, 11 Nov 2011 10:47:56 +0530 [thread overview]
Message-ID: <1320988680-7842-1-git-send-email-sathya.perla@emulex.com> (raw)
Pls apply. Thanks.
Sathya Perla (4):
be2net: init (vf)_if_handle/vf_pmac_id to handle failure scenarios
be2net: stop checking the UE registers after an EEH error
be2net: don't log more than one error on detecting EEH/UE errors
be2net: stop issuing FW cmds if any cmd times out
drivers/net/ethernet/emulex/benet/be.h | 16 ++++---
drivers/net/ethernet/emulex/benet/be_cmds.c | 49 +++++++-------------
drivers/net/ethernet/emulex/benet/be_cmds.h | 4 +-
drivers/net/ethernet/emulex/benet/be_main.c | 66 ++++++++++++++++-----------
4 files changed, 69 insertions(+), 66 deletions(-)
--
1.7.4
next reply other threads:[~2011-11-11 5:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 5:17 Sathya Perla [this message]
2011-11-11 5:17 ` [PATCH net-next 1/4] be2net: init (vf)_if_handle/vf_pmac_id to handle failure scenarios Sathya Perla
2011-11-11 5:17 ` [PATCH net-next 2/4] be2net: stop checking the UE registers after an EEH error Sathya Perla
2011-11-11 5:17 ` [PATCH net-next 3/4] be2net: don't log more than one error on detecting EEH/UE errors Sathya Perla
2011-11-11 5:18 ` [PATCH net-next 4/4] be2net: stop issuing FW cmds if any cmd times out Sathya Perla
2011-11-12 22:59 ` [PATCH net-next 0/4] be2net fixes David Miller
[not found] <1335965986-31886-1-git-send-email-somnath.kotur@emulex.com>
2012-05-02 14:04 ` Somnath.Kotur
-- strict thread matches above, loose matches on Subject: below --
2012-05-02 13:39 Somnath Kotur
2012-05-03 1:07 ` David Miller
2011-10-24 12:44 [PATCH net-next 0/4] be2net: fixes Sathya Perla
2011-10-24 22:35 ` David Miller
2011-10-25 4:49 ` Sathya.Perla
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=1320988680-7842-1-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.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 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).