From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kamil Vojanec <vojanec@cesnet.cz>
Subject: |WARNING| pw139247 [PATCH 1/2] net/bonding: introduce direct link bonding mode
Date: Fri, 12 Apr 2024 14:22:14 +0200 (CEST) [thread overview]
Message-ID: <20240412122214.7E67D121EEE@dpdk.org> (raw)
In-Reply-To: <20240412122006.101673-1-vojanec@cesnet.cz>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/139247
_coding style issues_
WARNING:BRACES: braces {} are not necessary for single statement blocks
#106: FILE: app/test/test_link_bonding.c:2162:
+ for (i = 0; i < burst_size; i++) {
+ pkts[i]->port = member_port_id;
+ }
WARNING:TYPO_SPELLING: 'expeected' may be misspelled - perhaps 'expected'?
#119: FILE: app/test/test_link_bonding.c:2175:
+ "Bonding port (%d) opackets value (%u) not as expeected (%u)
",
WARNING:TYPO_SPELLING: 'expeected' may be misspelled - perhaps 'expected'?
#126: FILE: app/test/test_link_bonding.c:2182:
+ "Member port (%d) opackets value (%u) not as expeected (%u)
",
WARNING:BRACES: braces {} are not necessary for single statement blocks
#170: FILE: app/test/test_link_bonding.c:2226:
+ for (i = 0; i < burst_size; i++) {
+ pkts[i]->port = exp_member_port_id;
+ }
WARNING:TYPO_SPELLING: 'expeected' may be misspelled - perhaps 'expected'?
#183: FILE: app/test/test_link_bonding.c:2239:
+ "Bonding port (%d) opackets value (%u) not as expeected (%u)
",
WARNING:BRACES: braces {} are not necessary for single statement blocks
#245: FILE: app/test/test_link_bonding.c:2301:
+ for (i = 0; i < burst_size; i++) {
+ pkts[i]->port = RTE_MAX_ETHPORTS;
+ }
WARNING:TYPO_SPELLING: 'expeected' may be misspelled - perhaps 'expected'?
#258: FILE: app/test/test_link_bonding.c:2314:
+ "Bonding port (%d) opackets value (%u) not as expeected (%u)
",
total: 0 errors, 7 warnings, 0 checks, 373 lines checked
parent reply other threads:[~2024-04-12 12:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240412122006.101673-1-vojanec@cesnet.cz>]
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=20240412122214.7E67D121EEE@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=vojanec@cesnet.cz \
/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).