From: "Dmitry Kravkov" <dmitry@broadcom.com>
To: ariele@broadcom.com, eilong@broadcom.com, davem@davemloft.net,
netdev@vger.kernel.org
Cc: "Dmitry Kravkov" <dmitry@broadcom.com>
Subject: [PATCH net 0/7] bnx2x: fixes
Date: Wed, 31 Oct 2012 17:46:51 +0200 [thread overview]
Message-ID: <1351698418-10005-1-git-send-email-dmitry@broadcom.com> (raw)
Hi Dave
Please consider applying the series of fixes to net.
Dmitry Kravkov (1):
bnx2x: disable FCoE for 57840 since not yet supported by FW
Yaniv Rosner (6):
bnx2x: Fix 57810 1G-KR link against certain switches.
bnx2x: Fix link down in 57712 following LFA
bnx2x: Restore global registers back to default.
bnx2x: Fix potential incorrect link speed provision
bnx2x: Fix unrecognized SFP+ module after driver is loaded
bnx2x: Fix no link on 577xx 10G-baseT
drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.c | 158 +++++++++++++++------
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 10 ++-
2 files changed, 122 insertions(+), 46 deletions(-)
Thanks,
Dmitry
next reply other threads:[~2012-10-31 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 15:46 Dmitry Kravkov [this message]
2012-10-31 15:46 ` [PATCH net 1/7] bnx2x: Fix 57810 1G-KR link against certain switches Dmitry Kravkov
2012-10-31 15:46 ` [PATCH net 2/7] bnx2x: Fix link down in 57712 following LFA Dmitry Kravkov
2012-10-31 15:46 ` [PATCH net 3/7] bnx2x: Restore global registers back to default Dmitry Kravkov
2012-10-31 15:46 ` [PATCH net 4/7] bnx2x: Fix potential incorrect link speed provision Dmitry Kravkov
2012-10-31 15:46 ` [PATCH net 5/7] bnx2x: Fix unrecognized SFP+ module after driver is loaded Dmitry Kravkov
2012-10-31 15:46 ` [PATCH net 6/7] bnx2x: Fix no link on 577xx 10G-baseT Dmitry Kravkov
2012-10-31 15:46 ` [PATCH net 7/7] bnx2x: Disable FCoE for 57840 since not yet supported by FW Dmitry Kravkov
2012-11-01 15:33 ` [PATCH net 0/7] bnx2x: 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=1351698418-10005-1-git-send-email-dmitry@broadcom.com \
--to=dmitry@broadcom.com \
--cc=ariele@broadcom.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.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).