From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 00/11] bnxt patch set
Date: Thu, 6 Feb 2025 10:47:00 -0800 [thread overview]
Message-ID: <CACZ4nhuM4nED67mapQoa3Yaf6MVAdZiNE1eVC0UKvAMm-1exfg@mail.gmail.com> (raw)
In-Reply-To: <20250205172004.50395-1-ajit.khaparde@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]
On Wed, Feb 5, 2025 at 9:20 AM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
>
> Patchset with bug fixes for bnxt PMD.
> Also addresses various Coverity issues reported in the recent
> Coverity scan.
>
> Please apply.
Patchset applied to dpdk-next-net-brcm subtree. Thanks
>
> Ajit Khaparde (4):
> net/bnxt: disable TruFlow if compressed CQE is set
> net/bnxt: simplify check for CQE mode
> net/bnxt: fix Rx handler
> net/bnxt: fix burst handler initialization
>
> Peter Spreadborough (6):
> net/bnxt: address coverity deadcode issue
> net/bnxt: address coverity checked return issues
> net/bnxt: address coverity overflow issues
> net/bnxt: address coverity integer overflow issues
> net/bnxt: address coverity uninitialized variables issues
> net/bnxt: address coverity control flow issues
>
> Sangtani Parag Satishbhai (1):
> net/bnxt/truFlow: Fix seg fault when rep are re-attached
>
> drivers/net/bnxt/bnxt.h | 4 -
> drivers/net/bnxt/bnxt_ethdev.c | 31 ++--
> drivers/net/bnxt/bnxt_hwrm.c | 2 +-
> drivers/net/bnxt/bnxt_rxr.c | 16 +-
> .../hcapi/cfa_v3/bld/p70/cfa_bld_p70_mpc.c | 90 +++++------
> .../p70/host/cfa_bld_p70_host_mpc_wrapper.c | 150 +++++++++---------
> drivers/net/bnxt/hcapi/cfa_v3/mm/cfa_mm.c | 6 +-
> drivers/net/bnxt/tf_core/v3/tfc_em.c | 1 +
> drivers/net/bnxt/tf_core/v3/tfc_tbl_scope.c | 2 +-
> drivers/net/bnxt/tf_ulp/bnxt_ulp_utils.h | 2 +-
> drivers/net/bnxt/tf_ulp/ulp_mapper.c | 10 +-
> drivers/net/bnxt/tf_ulp/ulp_rte_parser.c | 8 +-
> drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c | 1 +
> 13 files changed, 174 insertions(+), 149 deletions(-)
>
> --
> 2.39.5 (Apple Git-154)
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
prev parent reply other threads:[~2025-02-06 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 17:19 Ajit Khaparde
2025-02-05 17:19 ` [PATCH 01/11] net/bnxt: disable TruFlow if compressed CQE is set Ajit Khaparde
2025-02-05 17:19 ` [PATCH 02/11] net/bnxt: simplify check for CQE mode Ajit Khaparde
2025-02-05 17:19 ` [PATCH 03/11] net/bnxt: fix Rx handler Ajit Khaparde
2025-02-05 17:19 ` [PATCH 04/11] net/bnxt: set burst handler correctly Ajit Khaparde
2025-02-05 17:19 ` [PATCH 05/11] net/bnxt/truFlow: Fix seg fault when rep are re-attached Ajit Khaparde
2025-02-05 17:19 ` [PATCH 06/11] net/bnxt: address coverity deadcode issue Ajit Khaparde
2025-02-05 17:20 ` [PATCH 07/11] net/bnxt: address coverity checked return issues Ajit Khaparde
2025-02-05 17:20 ` [PATCH 08/11] net/bnxt: address coverity overflow issues Ajit Khaparde
2025-02-05 17:20 ` [PATCH 09/11] net/bnxt: address coverity integer " Ajit Khaparde
2025-02-05 17:20 ` [PATCH 10/11] net/bnxt: address coverity uninitialized variables issues Ajit Khaparde
2025-02-05 17:20 ` [PATCH 11/11] net/bnxt: address coverity control flow issues Ajit Khaparde
2025-02-06 18:47 ` 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=CACZ4nhuM4nED67mapQoa3Yaf6MVAdZiNE1eVC0UKvAMm-1exfg@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).