From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gavin Li <gavinl@nvidia.com>
Subject: |WARNING| pw143689 [PATCH 3/3] net/mlx5/hws: print CQE error syndrome and more information
Date: Fri, 6 Sep 2024 12:23:16 +0200 (CEST) [thread overview]
Message-ID: <20240906102316.46DDD121D10@dpdk.org> (raw)
In-Reply-To: <20240906102151.171965-4-gavinl@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143689
_coding style issues_
WARNING:TYPO_SPELLING: 'Vender' may be misspelled - perhaps 'Vendor'?
#145: FILE: drivers/net/mlx5/hws/mlx5dr_send.c:604:
+ DR_LOG(ERR, "CQE ERR:0x%x, Vender_ERR:0x%x, OP:0x%x, QPN:0x%x, WQE_CNT:0x%x",
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email name mismatch: 'From: Minggang Li(Gavin) <gavinl@nvidia.com>' != 'Signed-off-by: Gavin Li <gavinl@nvidia.com>'
total: 0 errors, 2 warnings, 0 checks, 16 lines checked
next prev parent reply other threads:[~2024-09-06 10:23 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240906102151.171965-4-gavinl@nvidia.com>
2024-09-06 9:55 ` |SUCCESS| pw143688-143689 " qemudev
2024-09-06 10:00 ` qemudev
2024-09-06 10:23 ` checkpatch [this message]
2024-09-06 11:24 ` |SUCCESS| pw143689 " 0-day Robot
2024-09-06 11:35 ` |PENDING| pw143688-143689 [PATCH] [3/3] net/mlx5/hws: print CQE erro dpdklab
2024-09-06 12:03 ` |SUCCESS| " dpdklab
2024-09-06 12:09 ` dpdklab
2024-09-06 13:18 ` dpdklab
2024-09-06 13:23 ` dpdklab
2024-09-06 13:47 ` |PENDING| " dpdklab
2024-09-06 14:02 ` dpdklab
2024-09-06 14:13 ` |SUCCESS| " dpdklab
2024-09-06 14:34 ` dpdklab
2024-09-06 14:36 ` dpdklab
2024-09-06 14:37 ` dpdklab
2024-09-06 14:37 ` dpdklab
2024-09-06 15:02 ` dpdklab
2024-09-06 15:08 ` |PENDING| " dpdklab
2024-09-06 15:19 ` |SUCCESS| " dpdklab
2024-09-06 15:26 ` dpdklab
2024-09-06 16:35 ` dpdklab
2024-09-06 18:41 ` |WARNING| " dpdklab
2024-09-06 19:43 ` |SUCCESS| " dpdklab
2024-09-06 19:47 ` dpdklab
2024-09-06 19:49 ` dpdklab
2024-09-06 20:01 ` dpdklab
2024-09-06 20:01 ` dpdklab
2024-09-06 21:39 ` dpdklab
2024-09-06 21:40 ` dpdklab
2024-09-06 21:47 ` dpdklab
2024-09-06 23:20 ` dpdklab
2024-09-06 23:46 ` dpdklab
2024-09-06 23:53 ` dpdklab
2024-09-06 23:57 ` dpdklab
2024-09-07 0:02 ` dpdklab
2024-09-07 0:06 ` dpdklab
2024-09-07 0:33 ` dpdklab
2024-09-07 0:56 ` dpdklab
2024-09-07 4:03 ` |PENDING| " dpdklab
2024-09-07 4:14 ` |SUCCESS| " dpdklab
2024-09-07 4:16 ` dpdklab
2024-09-07 4:42 ` dpdklab
2024-09-07 5:43 ` dpdklab
2024-09-07 7:57 ` dpdklab
2024-09-07 8:45 ` dpdklab
2024-09-07 14:46 ` dpdklab
2024-09-07 17:32 ` dpdklab
2024-09-08 0:05 ` dpdklab
2024-09-08 0:37 ` dpdklab
2024-09-17 10:06 ` dpdklab
2024-09-17 10:27 ` dpdklab
2024-09-17 10:40 ` dpdklab
2024-09-17 11:01 ` dpdklab
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=20240906102316.46DDD121D10@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=gavinl@nvidia.com \
--cc=test-report@dpdk.org \
/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).