All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/2] bnxt fixes
Date: Fri, 22 May 2020 23:12:07 +0530	[thread overview]
Message-ID: <20200522174209.19402-1-kalesh-anakkur.purayil@broadcom.com> (raw)
In-Reply-To: <20200522173254.18643-2-kalesh-anakkur.purayil@broadcom.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 629 bytes --]

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

These are two bug fixes observed during regression testing
with DPDK 20.05-rc3.

Please apply.

V2: fixed commit message and added Reviewed-by tag.

Kalesh AP (1):
  net/bnxt: fix the check for validating link speed

Rahul Gupta (1):
  net/bnxt: performance fix for Arm

 drivers/net/bnxt/bnxt.h        |  1 +
 drivers/net/bnxt/bnxt_cpr.h    |  6 +++---
 drivers/net/bnxt/bnxt_ethdev.c |  2 +-
 drivers/net/bnxt/bnxt_hwrm.c   | 14 +++++++++-----
 drivers/net/bnxt/bnxt_ring.h   | 24 +++++++++++++-----------
 5 files changed, 27 insertions(+), 20 deletions(-)

-- 
2.10.1


  reply	other threads:[~2020-05-22 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 17:32 [dpdk-dev] [PATCH 0/2] bnxt bug fixes Kalesh A P
2020-05-22 17:32 ` [dpdk-dev] [PATCH 1/2] net/bnxt: fix the check for validating link speed Kalesh A P
2020-05-22 17:42   ` Kalesh A P [this message]
2020-05-22 17:42     ` [dpdk-dev] [PATCH v2 " Kalesh A P
2020-05-22 17:42     ` [dpdk-dev] [PATCH v2 2/2] net/bnxt: performance fix for Arm Kalesh A P
2020-05-22 21:22     ` [dpdk-dev] [PATCH v2 0/2] bnxt fixes Ajit Khaparde
2020-05-22 17:32 ` [dpdk-dev] [PATCH 2/2] net/bnxt: performance fix for ARM 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=20200522174209.19402-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.