From: Raslan Darawsheh <rasland@nvidia.com>
To: "Minggang(Gavin) Li" <gavinl@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH V3 0/3] Error report improvement and fix
Date: Wed, 25 Sep 2024 08:23:58 +0000 [thread overview]
Message-ID: <CH3PR12MB84600DC5BF5828A39BF90AB6CF692@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240924105258.58037-1-gavinl@nvidia.com>
Hi,
From: Minggang(Gavin) Li <gavinl@nvidia.com>
Sent: Tuesday, September 24, 2024 1:52 PM
To: Matan Azrad; Slava Ovsiienko; Ori Kam; NBU-Contact-Thomas Monjalon (EXTERNAL)
Cc: dev@dpdk.org; Raslan Darawsheh
Subject: [PATCH V3 0/3] Error report improvement and fix
This patch set is to improve error handling in pmd and under layer.
Gavin Li (3):
net/mlx5: set rte errno if malloc failed
---
changelog:
v0->v1
- Fix typo in commit message
v1->v2
- Fix checkpatch warning
---
net/mlx5/hws: add log for failing to create rule in HWS
---
changelog:
v1->v2
- Fix checkpatch warning
v2->v3
- Fix checkpatch warning
---
net/mlx5/hws: print CQE error syndrome and more information
---
changelog:
v1->v2
- Fix checkpatch warning
v2->v3
- Fix checkpatch warning
---
drivers/net/mlx5/hws/mlx5dr_rule.c | 6 ++++++
drivers/net/mlx5/hws/mlx5dr_send.c | 9 ++++++++-
drivers/net/mlx5/mlx5_flow_hw.c | 31 +++++++++++++++++++++++-------
3 files changed, 38 insertions(+), 8 deletions(-)
--
2.34.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2024-09-25 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:21 [PATCH " Gavin Li
2024-09-06 10:21 ` [PATCH 1/3] net/mlx5: set rte errno if malloc failed Gavin Li
2024-09-06 10:21 ` [PATCH 2/3] net/mlx5/hws: add log for failing to create rule in HWS Gavin Li
2024-09-06 10:21 ` [PATCH 3/3] net/mlx5/hws: print CQE error syndrome and more information Gavin Li
2024-09-10 7:58 ` [PATCH V1 0/3] Error report improvement and fix Gavin Li
2024-09-10 7:58 ` [PATCH V1 1/3] net/mlx5: set rte errno if malloc failed Gavin Li
2024-09-10 7:58 ` [PATCH V1 2/3] net/mlx5/hws: add log for failing to create rule in HWS Gavin Li
2024-09-10 7:58 ` [PATCH V1 3/3] net/mlx5/hws: print CQE error syndrome and more information Gavin Li
2024-09-24 5:59 ` [PATCH V2 0/3] Error report improvement and fix Minggang Li(Gavin)
2024-09-24 5:59 ` [PATCH V2 1/3] net/mlx5: set rte errno if malloc failed Minggang Li(Gavin)
2024-09-24 5:59 ` [PATCH V2 2/3] net/mlx5/hws: add log for failing to create rule in HWS Minggang Li(Gavin)
2024-09-24 5:59 ` [PATCH V2 3/3] net/mlx5/hws: print CQE error syndrome and more information Minggang Li(Gavin)
2024-09-24 10:52 ` [PATCH V3 0/3] Error report improvement and fix Minggang Li(Gavin)
2024-09-24 10:52 ` [PATCH V3 1/3] net/mlx5: set rte errno if malloc failed Minggang Li(Gavin)
2024-09-24 10:52 ` [PATCH V3 2/3] net/mlx5/hws: add log for failing to create rule in HWS Minggang Li(Gavin)
2024-09-24 10:52 ` [PATCH V3 3/3] net/mlx5/hws: print CQE error syndrome and more information Minggang Li(Gavin)
2024-09-25 8:23 ` Raslan Darawsheh [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=CH3PR12MB84600DC5BF5828A39BF90AB6CF692@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=gavinl@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).