From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] bnxt fixes
Date: Fri, 22 May 2020 14:22:30 -0700 [thread overview]
Message-ID: <CACZ4nhtTjr7scYXCH2GPiSO5LhA3L_xNCAgE4wDnhvKJA89K9g@mail.gmail.com> (raw)
In-Reply-To: <20200522174209.19402-1-kalesh-anakkur.purayil@broadcom.com>
On Fri, May 22, 2020 at 10:26 AM Kalesh A P <
kalesh-anakkur.purayil@broadcom.com> wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> These are two bug fixes observed during regression testing
> with DPDK 20.05-rc3.
>
> Please apply.
>
Patches applied to dpdk-next-net-brcm. Thanks
>
> 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
>
>
next prev parent reply other threads:[~2020-05-22 21:22 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 ` [dpdk-dev] [PATCH v2 0/2] bnxt fixes Kalesh A P
2020-05-22 17:42 ` [dpdk-dev] [PATCH v2 1/2] net/bnxt: fix the check for validating link speed 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 ` Ajit Khaparde [this message]
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=CACZ4nhtTjr7scYXCH2GPiSO5LhA3L_xNCAgE4wDnhvKJA89K9g@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kalesh-anakkur.purayil@broadcom.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).