From: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, ajit.khaparde@broadcom.com
Subject: [dpdk-dev] [PATCH 0/6] bnxt bug fixes
Date: Fri, 28 Aug 2020 10:31:06 +0530 [thread overview]
Message-ID: <20200828050112.19482-1-kalesh-anakkur.purayil@broadcom.com> (raw)
From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
This patchset contains bnxt bug fixes.
Kalesh AP (5):
net/bnxt: fix endianness while setting L4 destination port
net/bnxt: fix to initialize structure variable
net/bnxt: fix a possible segfault in vector mode Tx path
net/bnxt: fix L2 filter alloc
net/bnxt: fix speed setting on BCM957508-N2100 adapters
Venkat Duvvuru (1):
net/bnxt: fix LRO configuration
drivers/net/bnxt/bnxt.h | 4 ++++
drivers/net/bnxt/bnxt_ethdev.c | 44 +++++++++++++++++++++++------------
drivers/net/bnxt/bnxt_hwrm.c | 15 ++++++++----
drivers/net/bnxt/bnxt_ring.c | 1 +
drivers/net/bnxt/bnxt_rxr.c | 3 +++
drivers/net/bnxt/bnxt_rxtx_vec_neon.c | 2 ++
drivers/net/bnxt/bnxt_rxtx_vec_sse.c | 2 ++
drivers/net/bnxt/bnxt_txr.c | 2 ++
8 files changed, 53 insertions(+), 20 deletions(-)
--
2.10.1
next reply other threads:[~2020-08-28 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 5:01 Kalesh A P [this message]
2020-08-28 5:01 ` [dpdk-dev] [PATCH 1/6] net/bnxt: fix endianness while setting L4 destination port Kalesh A P
2020-08-28 5:01 ` [dpdk-dev] [PATCH 2/6] net/bnxt: fix LRO configuration Kalesh A P
2020-08-28 5:01 ` [dpdk-dev] [PATCH 3/6] net/bnxt: fix to initialize structure variable Kalesh A P
2020-08-28 5:01 ` [dpdk-dev] [PATCH 4/6] net/bnxt: fix a possible segfault in vector mode Tx path Kalesh A P
2020-08-28 5:01 ` [dpdk-dev] [PATCH 5/6] net/bnxt: fix L2 filter alloc Kalesh A P
2020-08-28 5:01 ` [dpdk-dev] [PATCH 6/6] net/bnxt: fix speed setting on BCM957508-N2100 adapters Kalesh A P
2020-09-02 19:15 ` [dpdk-dev] [PATCH 0/6] bnxt bug fixes Ajit Khaparde
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=20200828050112.19482-1-kalesh-anakkur.purayil@broadcom.com \
--to=kalesh-anakkur.purayil@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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).