From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com
Subject: Re: [dpdk-dev] [PATCH 0/3] bnxt PMD fixes
Date: Mon, 6 Feb 2023 09:29:43 -0800 [thread overview]
Message-ID: <CACZ4nhuJ1+MV-3YzqS4iG5coBmrLSBa8oEyUj4j509M-OcLvtQ@mail.gmail.com> (raw)
In-Reply-To: <20230201042014.23526-1-kalesh-anakkur.purayil@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
On Tue, Jan 31, 2023 at 8:23 PM Kalesh A P
<kalesh-anakkur.purayil@broadcom.com> wrote:
>
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> This patchset contains bnxt PMD bug fixes. Please apply.
Patchset applied dpdk-next-net-brcm. Thanks
>
> Kalesh AP (1):
> net/bnxt: fix Tx queue stats after queue stop and start
>
> Mike Baucom (1):
> net/bnxt: fix Rx queue stats after queue stop and start
>
> Venkat Duvvuru (1):
> net/bnxt: do not corrupt RSS hash value in the mbuf
>
> drivers/net/bnxt/bnxt_rxq.c | 6 ++++++
> drivers/net/bnxt/bnxt_rxr.c | 1 -
> drivers/net/bnxt/bnxt_txr.c | 6 ++++++
> 3 files changed, 12 insertions(+), 1 deletion(-)
>
> --
> 2.10.1
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
prev parent reply other threads:[~2023-02-06 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 4:20 Kalesh A P
2023-02-01 4:20 ` [dpdk-dev] [PATCH 1/3] net/bnxt: fix Tx queue stats after queue stop and start Kalesh A P
2023-02-01 4:20 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix Rx " Kalesh A P
2023-02-01 4:20 ` [dpdk-dev] [PATCH 3/3] net/bnxt: do not corrupt RSS hash value in the mbuf Kalesh A P
2023-02-06 17: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=CACZ4nhuJ1+MV-3YzqS4iG5coBmrLSBa8oEyUj4j509M-OcLvtQ@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).