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/3] bnxt fixes
Date: Wed, 1 Sep 2021 17:35:34 -0700 [thread overview]
Message-ID: <CACZ4nhsUWzccSgVJm-x5dgP4yovy1_MEH=HEcHnZXOf8httOsQ@mail.gmail.com> (raw)
In-Reply-To: <20210823081214.9725-1-kalesh-anakkur.purayil@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
On Mon, Aug 23, 2021 at 12:51 AM Kalesh A P
<kalesh-anakkur.purayil@broadcom.com> wrote:
>
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> Please apply.
>
> Kalesh AP (3):
> net/bnxt: fix Rx mbuf VLAN in scalar Rx
> net/bnxt: check FW capability for VLAN offloads
> net/bnxt: fix VLAN indication in Rx mbuf
Patchset applied to dpdk-next-net-brcm.
>
> drivers/net/bnxt/bnxt.h | 7 ++++---
> drivers/net/bnxt/bnxt_ethdev.c | 4 ++++
> drivers/net/bnxt/bnxt_hwrm.c | 9 +++++++++
> drivers/net/bnxt/bnxt_rxr.c | 10 +++++++---
> drivers/net/bnxt/bnxt_rxr.h | 10 ++++++++++
> 5 files changed, 34 insertions(+), 6 deletions(-)
>
> --
> 2.10.1
>
next prev parent reply other threads:[~2021-09-02 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 8:12 Kalesh A P
2021-08-23 8:12 ` [dpdk-dev] [PATCH 1/3] net/bnxt: fix Rx mbuf VLAN in scalar Rx Kalesh A P
2021-08-23 8:12 ` [dpdk-dev] [PATCH 2/3] net/bnxt: check FW capability for VLAN offloads Kalesh A P
2021-08-23 8:12 ` [dpdk-dev] [PATCH 3/3] net/bnxt: fix VLAN indication in Rx mbuf Kalesh A P
2021-09-02 0:35 ` Ajit Khaparde [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-04 9:07 [dpdk-dev] [PATCH 0/3] bnxt fixes Kalesh A P
2021-03-12 0:11 ` 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='CACZ4nhsUWzccSgVJm-x5dgP4yovy1_MEH=HEcHnZXOf8httOsQ@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).