DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-dev]  [PATCH 0/5] bnxt patchset with bug fixes
Date: Wed, 30 Oct 2019 13:34:33 +0530	[thread overview]
Message-ID: <20191030080438.27530-1-kalesh-anakkur.purayil@broadcom.com> (raw)

From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>

Please apply.

Kalesh AP (3):
  net/bnxt: fix L4 checksum error indication in non-vector mode rx
  net/bnxt: fix a failure case during initialization
  net/bnxt: fix incorrect COS queue mapping

Santoshkumar Karanappa Rastapur (1):
  net/bnxt: fix vnic allocation failure on port toggle

Venkat Duvvuru (1):
  net/bnxt: refactor vlan filtering code

 drivers/net/bnxt/bnxt_ethdev.c | 126 +++++++++++++----------------------------
 drivers/net/bnxt/bnxt_filter.c |   4 +-
 drivers/net/bnxt/bnxt_filter.h |   8 ++-
 drivers/net/bnxt/bnxt_hwrm.c   |  14 ++---
 drivers/net/bnxt/bnxt_ring.c   |   5 +-
 drivers/net/bnxt/bnxt_ring.h   |   1 -
 drivers/net/bnxt/bnxt_rxq.c    |   2 +
 drivers/net/bnxt/bnxt_rxr.c    |  18 +++---
 drivers/net/bnxt/bnxt_vnic.c   |   5 +-
 drivers/net/bnxt/bnxt_vnic.h   |   1 -
 10 files changed, 73 insertions(+), 111 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-10-30  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  8:04 Kalesh A P [this message]
2019-10-30  8:04 ` [dpdk-dev] [PATCH 1/5] net/bnxt: fix L4 checksum error indication in non-vector mode rx Kalesh A P
2019-10-30  8:04 ` [dpdk-dev] [PATCH 2/5] net/bnxt: refactor vlan filtering code Kalesh A P
2019-10-30  8:04 ` [dpdk-dev] [PATCH 3/5] net/bnxt: fix vnic allocation failure on port toggle Kalesh A P
2019-10-30  8:04 ` [dpdk-dev] [PATCH 4/5] net/bnxt: fix a failure case during initialization Kalesh A P
2019-10-30  8:04 ` [dpdk-dev] [PATCH 5/5] net/bnxt: fix incorrect COS queue mapping Kalesh A P

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=20191030080438.27530-1-kalesh-anakkur.purayil@broadcom.com \
    --to=kalesh-anakkur.purayil@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).