From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH net 0/6] bnxt_en: Fixes for net.
Date: Tue, 10 Apr 2018 23:58:07 -0400 [thread overview]
Message-ID: <1523419093-18637-1-git-send-email-michael.chan@broadcom.com> (raw)
This bug fix series include NULL pointer fixes in ethtool -x code path
and in the error clean up path when freeing IRQs, a ring accounting bug
that missed rings used by the RDMA driver, and 3 bug fixes related to TC
Flower and VF-reps.
Andy Gospodarek (1):
bnxt_en: do not allow wildcard matches for L2 flows
Michael Chan (3):
bnxt_en: Fix ethtool -x crash when device is down.
bnxt_en: Need to include RDMA rings in bnxt_check_rings().
bnxt_en: Fix NULL pointer dereference at bnxt_free_irq().
Sriharsha Basavapatna (2):
bnxt_en: Ignore src port field in decap filter nodes
bnxt_en: Support max-mtu with VF-reps
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 4 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 11 ++--
drivers/net/ethernet/broadcom/bnxt/bnxt_tc.c | 63 ++++++++++++++++++++++-
drivers/net/ethernet/broadcom/bnxt/bnxt_vfr.c | 30 +++++++++++
4 files changed, 103 insertions(+), 5 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-04-11 3:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 3:58 Michael Chan [this message]
2018-04-11 3:58 ` [PATCH net 1/6] bnxt_en: Fix ethtool -x crash when device is down Michael Chan
2018-04-11 3:58 ` [PATCH net 2/6] bnxt_en: do not allow wildcard matches for L2 flows Michael Chan
2018-04-11 3:58 ` [PATCH net 3/6] bnxt_en: Ignore src port field in decap filter nodes Michael Chan
2018-04-11 3:58 ` [PATCH net 4/6] bnxt_en: Support max-mtu with VF-reps Michael Chan
2018-04-11 14:08 ` David Miller
2018-04-11 3:58 ` [PATCH net 5/6] bnxt_en: Need to include RDMA rings in bnxt_check_rings() Michael Chan
2018-04-11 3:58 ` [PATCH net 6/6] bnxt_en: Fix NULL pointer dereference at bnxt_free_irq() Michael Chan
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=1523419093-18637-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.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).