From: Rajesh Borundia <rajesh.borundia@qlogic.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <Dept_NX_Linux_NIC_Driver@qlogic.com>
Subject: [PATCH net 0/4] qlcnic: bug fixes
Date: Tue, 28 Jan 2014 11:55:26 -0500 [thread overview]
Message-ID: <1390928130-10710-1-git-send-email-rajesh.borundia@qlogic.com> (raw)
The patch series contains following bug fixes
o Bound checks for number of receive descriptors and number of recieve rings.
Both of these have off-by-one errors.
o Vlan list was getting re-initialized in case of adapter reset.
o Tx queue was timing out because of missing start queue for a corresponding
netif_tx_disable.
o Loopback test failed because driver was not setting linkup variable
while handling link events.
Please apply to net.
Manish Chopra (1):
qlcnic: Correct off-by-one errors in bounds checks
Rajesh Borundia (2):
qlcnic: Fix initialization of vlan list.
qlcnic: Fix tx timeout.
Shahed Shaikh (1):
qlcnic: Fix loopback test failure
drivers/net/ethernet/qlogic/qlcnic/qlcnic_io.c | 19 ++++++++++++-------
drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c | 9 ++-------
.../ethernet/qlogic/qlcnic/qlcnic_sriov_common.c | 11 +++++------
3 files changed, 19 insertions(+), 20 deletions(-)
next reply other threads:[~2014-01-28 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 16:55 Rajesh Borundia [this message]
2014-01-28 16:55 ` [PATCH net 1/4] qlcnic: Correct off-by-one errors in bounds checks Rajesh Borundia
2014-01-28 16:55 ` [PATCH net 2/4] qlcnic: Fix initialization of vlan list Rajesh Borundia
2014-01-28 16:55 ` [PATCH net 3/4] qlcnic: Fix tx timeout Rajesh Borundia
2014-01-28 16:55 ` [PATCH net 4/4] qlcnic: Fix loopback test failure Rajesh Borundia
2014-01-28 20:00 ` [PATCH net 0/4] qlcnic: bug fixes David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-09-22 9:51 [PATCH net 0/4] qlcnic: Bug fixes Manish Chopra
2014-09-26 19:12 ` David Miller
2013-07-26 20:23 [PATCH net 0/4] qlcnic: bug fixes Himanshu Madhani
2013-07-28 3:03 ` 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=1390928130-10710-1-git-send-email-rajesh.borundia@qlogic.com \
--to=rajesh.borundia@qlogic.com \
--cc=Dept_NX_Linux_NIC_Driver@qlogic.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;
as well as URLs for NNTP newsgroup(s).