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/4] bnxt fixes
Date: Mon, 24 Jan 2022 21:00:52 -0800 [thread overview]
Message-ID: <CACZ4nhv+Ku90upA+V75Tum40sqVn4pkQsz3M=8H8THW0QCZFhw@mail.gmail.com> (raw)
In-Reply-To: <20220120091228.7076-1-kalesh-anakkur.purayil@broadcom.com>
On Thu, Jan 20, 2022 at 12:53 AM Kalesh A P
<kalesh-anakkur.purayil@broadcom.com> wrote:
>
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> Please apply.
>
> Ajit Khaparde (1):
> net/bnxt: fix VF resource allocation strategy
>
> Kalesh AP (3):
> net/bnxt: fix check for autoneg enablement
> net/bnxt: handle ring cleanup in case of error
> net/bnxt: fix to alloc the memzone per VNIC
Patchset applied to dpdk-next-net-brcm. Thanks
>
> drivers/net/bnxt/bnxt_hwrm.c | 35 ++++++++++++-----------
> drivers/net/bnxt/bnxt_hwrm.h | 2 ++
> drivers/net/bnxt/bnxt_ring.c | 1 +
> drivers/net/bnxt/bnxt_vnic.c | 68 +++++++++++++++++++-------------------------
> drivers/net/bnxt/bnxt_vnic.h | 1 +
> 5 files changed, 52 insertions(+), 55 deletions(-)
>
> --
> 2.10.1
>
next prev parent reply other threads:[~2022-01-25 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 9:12 Kalesh A P
2022-01-20 9:12 ` [dpdk-dev] [PATCH 1/4] net/bnxt: fix check for autoneg enablement Kalesh A P
2022-01-20 9:12 ` [dpdk-dev] [PATCH 2/4] net/bnxt: handle ring cleanup in case of error Kalesh A P
2022-01-20 9:12 ` [dpdk-dev] [PATCH 3/4] net/bnxt: fix to alloc the memzone per VNIC Kalesh A P
2022-01-20 9:12 ` [dpdk-dev] [PATCH 4/4] net/bnxt: fix VF resource allocation strategy Kalesh A P
2022-01-25 5:00 ` Ajit Khaparde [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-09 3:13 [dpdk-dev] [PATCH 0/4] bnxt fixes Kalesh A P
2021-06-16 22:38 ` Ajit Khaparde
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+Ku90upA+V75Tum40sqVn4pkQsz3M=8H8THW0QCZFhw@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).