From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Maayan Kashani <mkashani@nvidia.com>
Subject: |WARNING| pw140550 [PATCH 1/6] net/mlx5: update NTA rule pattern and actions flags
Date: Sun, 2 Jun 2024 12:29:44 +0200 (CEST) [thread overview]
Message-ID: <20240602102944.A19AA12367B@dpdk.org> (raw)
In-Reply-To: <20240602102841.196990-1-mkashani@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140550
_coding style issues_
WARNING:BAD_SIGN_OFF: Duplicate signature
#353:
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
WARNING:TYPO_SPELLING: 'chaned' may be misspelled - perhaps 'changed'?
#457: FILE: drivers/net/mlx5/mlx5_flow.h:1333:
+ uint8_t chaned_flow;
WARNING:TYPO_SPELLING: 'chaned' may be misspelled - perhaps 'changed'?
#610: FILE: drivers/net/mlx5/mlx5_flow_hw.c:12903:
+ if (flow->nt2hws->chaned_flow)
WARNING:TYPO_SPELLING: 'chaned' may be misspelled - perhaps 'changed'?
#1208: FILE: drivers/net/mlx5/mlx5_nta_rss.c:549:
+ rss_next->nt2hws->chaned_flow = 1;
WARNING:BAD_SIGN_OFF: Duplicate signature
#1236:
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
WARNING:BAD_SIGN_OFF: Duplicate signature
#1389:
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
WARNING:BAD_SIGN_OFF: Duplicate signature
#1551:
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
WARNING:BAD_SIGN_OFF: Duplicate signature
#1636:
Signed-off-by: Gregory Etelson <getelson@nvidia.com>
total: 0 errors, 8 warnings, 0 checks, 1409 lines checked
next parent reply other threads:[~2024-06-02 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240602102841.196990-1-mkashani@nvidia.com>
2024-06-02 10:29 ` checkpatch [this message]
2024-06-03 7:45 ` |WARNING| pw140550-140579 " qemudev
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=20240602102944.A19AA12367B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mkashani@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).