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 V4 00/10] bnxt patchset with bug fixes
Date: Mon, 20 Jan 2020 13:03:04 -0800 [thread overview]
Message-ID: <CACZ4nhunj9u6qkhB-zw1Yv0E1BFvDnGg+tSHRT+R3YPDE3e3Fg@mail.gmail.com> (raw)
In-Reply-To: <20200116130455.30193-1-kalesh-anakkur.purayil@broadcom.com>
On Thu, Jan 16, 2020 at 4:47 AM Kalesh A P <
kalesh-anakkur.purayil@broadcom.com> wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> v1->v2: fixed the correct the commit ids in Fixes tag.
> v2->v3: shorten commit log and update commit ids for Fixes tag.
> v3->v4: addressed Ferruh's comment on Patch#1 and Pacth#9 and marked
> required patches for stable inclusion.
>
> Kalesh AP (8):
> net/bnxt: fix flow create failure
> net/bnxt: fix probe failure in FreeBSD
> net/bnxt: fix to use correct IOVA mapping
> net/bnxt: fix enable/disable VLAN filtering
> net/bnxt: fix VLAN strip support
> net/bnxt: handle hw filter setting when port is stopped
> net/bnxt: fix a memory leak in port stop
> net/bnxt: use macro for PCI log format
>
> Somnath Kotur (2):
> net/bnxt: release port upon close
> net/bnxt: fix to cap max rings to minimum of compl rings and stat
> contexts
>
> drivers/net/bnxt/bnxt.h | 21 +-
> drivers/net/bnxt/bnxt_ethdev.c | 468
> ++++++++++++++++++++++-------------------
> drivers/net/bnxt/bnxt_filter.c | 5 +-
> drivers/net/bnxt/bnxt_flow.c | 4 +-
> drivers/net/bnxt/bnxt_hwrm.c | 28 +--
> drivers/net/bnxt/bnxt_irq.c | 8 +
> drivers/net/bnxt/bnxt_ring.c | 17 --
> drivers/net/bnxt/bnxt_vnic.c | 11 -
> 8 files changed, 289 insertions(+), 273 deletions(-)
>
Patchset applied to dpdk-next-net-brcm.
>
> --
> 2.10.1
>
>
prev parent reply other threads:[~2020-01-20 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 13:04 Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 01/10] net/bnxt: fix flow create failure Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 02/10] net/bnxt: fix probe failure in FreeBSD Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 03/10] net/bnxt: fix to use correct IOVA mapping Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 04/10] net/bnxt: fix enable/disable VLAN filtering Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 05/10] net/bnxt: fix VLAN strip support Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 06/10] net/bnxt: handle hw filter setting when port is stopped Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 07/10] net/bnxt: fix a memory leak in port stop Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 08/10] net/bnxt: use macro for PCI log format Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 09/10] net/bnxt: release port upon close Kalesh A P
2020-01-16 13:04 ` [dpdk-dev] [PATCH V4 10/10] net/bnxt: fix to cap max rings to minimum of compl rings and stat contexts Kalesh A P
2020-01-20 21:03 ` 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=CACZ4nhunj9u6qkhB-zw1Yv0E1BFvDnGg+tSHRT+R3YPDE3e3Fg@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).