From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bing Zhao <bingz@nvidia.com>
Subject: |WARNING| pw141123 [PATCH] net/mlx5: add non-template flow metadata split
Date: Thu, 13 Jun 2024 14:53:48 +0200 (CEST) [thread overview]
Message-ID: <20240613125348.9845E124124@dpdk.org> (raw)
In-Reply-To: <20240613125146.547992-1-bingz@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/141123
_coding style issues_
WARNING:TYPO_SPELLING: 'chaned' may be misspelled - perhaps 'changed'?
#467: FILE: drivers/net/mlx5/mlx5_flow_hw.c:13738:
+ if (!flow || !flow->nt2hws || flow->nt2hws->chaned_flow)
WARNING:TYPO_SPELLING: 'chaned' may be misspelled - perhaps 'changed'?
#568: FILE: drivers/net/mlx5/mlx5_flow_hw.c:13858:
+ flow->nt2hws->chaned_flow = 1;
total: 0 errors, 2 warnings, 0 checks, 967 lines checked
next prev parent reply other threads:[~2024-06-13 12:53 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240613125146.547992-1-bingz@nvidia.com>
2024-06-13 12:29 ` |SUCCESS| " qemudev
2024-06-13 12:34 ` qemudev
2024-06-13 12:53 ` checkpatch [this message]
2024-06-13 16:04 ` |WARNING| pw141123 [PATCH] net/mlx5: add non-template flow metadata dpdklab
2024-06-13 16:04 ` dpdklab
2024-06-13 16:05 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:06 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:44 ` dpdklab
2024-06-13 16:46 ` |FAILURE| " dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:49 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` |WARNING| " dpdklab
2024-06-13 16:52 ` |FAILURE| " dpdklab
2024-06-13 16:54 ` dpdklab
2024-06-13 16:55 ` dpdklab
2024-06-13 16:55 ` dpdklab
2024-06-13 16:56 ` dpdklab
2024-06-13 16:57 ` dpdklab
2024-06-13 16:57 ` dpdklab
2024-06-13 16:59 ` dpdklab
2024-06-13 16:59 ` dpdklab
2024-06-13 16:59 ` dpdklab
2024-06-13 17:00 ` dpdklab
2024-06-13 17:00 ` dpdklab
2024-06-13 17:04 ` dpdklab
2024-06-13 17:06 ` dpdklab
2024-06-13 17:07 ` dpdklab
2024-06-13 17:08 ` dpdklab
2024-06-13 17:09 ` dpdklab
2024-06-13 17:09 ` dpdklab
2024-06-13 17:10 ` dpdklab
2024-06-13 17:10 ` dpdklab
2024-06-13 17:18 ` dpdklab
2024-06-13 17:22 ` dpdklab
2024-06-13 17:22 ` dpdklab
2024-06-13 17:22 ` dpdklab
2024-06-13 17:23 ` dpdklab
2024-06-13 17:23 ` dpdklab
2024-06-13 17:24 ` dpdklab
2024-06-13 17:25 ` dpdklab
2024-06-13 17:25 ` dpdklab
2024-06-13 17:26 ` dpdklab
2024-06-13 17:26 ` dpdklab
2024-06-13 17:27 ` dpdklab
2024-06-13 17:28 ` dpdklab
2024-06-13 17:28 ` dpdklab
2024-06-13 17:29 ` dpdklab
2024-06-13 17:29 ` dpdklab
2024-06-13 17:30 ` dpdklab
2024-06-13 17:31 ` dpdklab
2024-06-13 17:32 ` dpdklab
2024-06-13 17:34 ` dpdklab
2024-06-13 17:35 ` dpdklab
2024-06-13 17:38 ` dpdklab
2024-06-13 17:39 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:44 ` 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=20240613125348.9845E124124@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bingz@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).