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 0/5] bnxt bug fixes
Date: Fri, 10 Jul 2020 07:05:43 -0700 [thread overview]
Message-ID: <CACZ4nhv_qijsQSGax4GaLMtD-ZhTA0=B+87n+1=kSTZ+sFYE9A@mail.gmail.com> (raw)
In-Reply-To: <20200709093832.7616-1-kalesh-anakkur.purayil@broadcom.com>
On Thu, Jul 9, 2020 at 2:23 AM Kalesh A P <
kalesh-anakkur.purayil@broadcom.com> wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> This patchset contains few bug fixes in bnxt PMD.
>
> Please apply.
>
> Kalesh AP (5):
> net/bnxt: fix to avoid unnecessary memory allocation
> net/bnxt: remove unused enum declaration
> net/bnxt: fix to not send unnecessary hwrm command
> net/bnxt: fix to set flow error when filter create fails
> net/bnxt: fix to free filters when flow create fails
>
> drivers/net/bnxt/bnxt.h | 9 ------
> drivers/net/bnxt/bnxt_ethdev.c | 10 ++++---
> drivers/net/bnxt/bnxt_flow.c | 35 +++++++++++++++--------
> drivers/net/bnxt/bnxt_hwrm.c | 63
> ++++++++++++++----------------------------
> drivers/net/bnxt/bnxt_hwrm.h | 3 +-
> 5 files changed, 52 insertions(+), 68 deletions(-)
>
Patchset applied to dpdk-next-net-brcm. Thanks
>
> --
> 2.10.1
>
>
prev parent reply other threads:[~2020-07-10 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 9:38 Kalesh A P
2020-07-09 9:38 ` [dpdk-dev] [PATCH 1/5] net/bnxt: fix to avoid unnecessary memory allocation Kalesh A P
2020-07-09 9:38 ` [dpdk-dev] [PATCH 2/5] net/bnxt: remove unused enum declaration Kalesh A P
2020-07-09 9:38 ` [dpdk-dev] [PATCH 3/5] net/bnxt: fix to not send unnecessary hwrm command Kalesh A P
2020-07-09 9:38 ` [dpdk-dev] [PATCH 4/5] net/bnxt: fix to set flow error when filter create fails Kalesh A P
2020-07-09 9:38 ` [dpdk-dev] [PATCH 5/5] net/bnxt: fix to free filters when flow " Kalesh A P
2020-07-10 14:05 ` Ajit Khaparde [this message]
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='CACZ4nhv_qijsQSGax4GaLMtD-ZhTA0=B+87n+1=kSTZ+sFYE9A@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).