From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] bnxt PMD patches
Date: Wed, 14 Jul 2021 17:29:27 -0700 [thread overview]
Message-ID: <CACZ4nhsSJpewNrAvEecX6zgxFeewERxoOHEWFwRie+7n1TEC1g@mail.gmail.com> (raw)
In-Reply-To: <20210712080435.9149-1-kalesh-anakkur.purayil@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Mon, Jul 12, 2021 at 12:43 AM Kalesh A P <
kalesh-anakkur.purayil@broadcom.com> wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> Please apply.
>
Patchset applied to dpdk-next-net-brcm.
>
> Kalesh AP (2):
> net/bnxt: update HSI structure
> net/bnxt: inform firmware about host MTU
>
> Somnath Kotur (2):
> net/bnxt: minor refactoring of async handling code
> net/bnxt: add handler for pause storm event
>
> drivers/net/bnxt/bnxt.h | 5 +
> drivers/net/bnxt/bnxt_cpr.c | 41 +-
> drivers/net/bnxt/bnxt_ethdev.c | 3 +
> drivers/net/bnxt/bnxt_hwrm.c | 41 +-
> drivers/net/bnxt/bnxt_hwrm.h | 3 +
> drivers/net/bnxt/hsi_struct_def_dpdk.h | 1202
> ++++++++++++++++++++++++++++++--
> 6 files changed, 1232 insertions(+), 63 deletions(-)
>
> --
> 2.10.1
>
>
prev parent reply other threads:[~2021-07-15 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 8:04 Kalesh A P
2021-07-12 8:04 ` [dpdk-dev] [PATCH 1/4] net/bnxt: update HSI structure Kalesh A P
2021-07-12 8:04 ` [dpdk-dev] [PATCH 2/4] net/bnxt: inform firmware about host MTU Kalesh A P
2021-07-12 8:04 ` [dpdk-dev] [PATCH 3/4] net/bnxt: minor refactoring of async handling code Kalesh A P
2021-07-12 8:04 ` [dpdk-dev] [PATCH 4/4] net/bnxt: add handler for pause storm event Kalesh A P
2021-07-15 0:29 ` 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=CACZ4nhsSJpewNrAvEecX6zgxFeewERxoOHEWFwRie+7n1TEC1g@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--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).