From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: |WARNING| pw143724 [RFCv2 6/6] examples/l3fwd: make ACL work in pipeline and eventdev modes
Date: Fri, 6 Sep 2024 15:16:00 +0200 (CEST) [thread overview]
Message-ID: <20240906131600.D0D4E121D10@dpdk.org> (raw)
In-Reply-To: <20240906131348.804-7-konstantin.v.ananyev@yandex.ru>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143724
_coding style issues_
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#101:
'wqorder' mode is implemtened using rte_soring structure per queue.
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#106:
Possible values one of: poll/eventdev/wqorder/wqorderS/wqunorder/wqunorderS
WARNING:TYPO_SPELLING: 'oen' may be misspelled - perhaps 'one'?
#113:
- wqunorderS: Worker-Pool un-ordered mode with oen work queue per I/O thread.
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#156: FILE: examples/l3fwd/l3fwd.h:82:
+ L3FWD_WORKER_UNQUE,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#177: FILE: examples/l3fwd/l3fwd.h:103:
+ struct rte_soring *sor;
WARNING:TYPO_SPELLING: 'thred' may be misspelled - perhaps 'thread'?
#178: FILE: examples/l3fwd/l3fwd.h:104:
+ /* used by WQ, sort of thred-local var */
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#857: FILE: examples/l3fwd/l3fwd_wqp.c:23:
+wqp_soring_init(struct rte_soring **r, struct rte_soring_param *prm, size_t sz,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#857: FILE: examples/l3fwd/l3fwd_wqp.c:23:
+wqp_soring_init(struct rte_soring **r, struct rte_soring_param *prm, size_t sz,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#857: FILE: examples/l3fwd/l3fwd_wqp.c:23:
+wqp_soring_init(struct rte_soring **r, struct rte_soring_param *prm, size_t sz,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#868: FILE: examples/l3fwd/l3fwd_wqp.c:34:
+ return rte_soring_init(*r, prm);
WARNING:TYPO_SPELLING: 'unque' may be misspelled - perhaps 'unique'?
#888: FILE: examples/l3fwd/l3fwd_wqp.c:54:
+l3fwd_wqp_unque_init(struct lcore_conf *lc, const struct l3fwd_wqp_param *prm,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#937: FILE: examples/l3fwd/l3fwd_wqp.c:103:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#951: FILE: examples/l3fwd/l3fwd_wqp.c:117:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#962: FILE: examples/l3fwd/l3fwd_wqp.c:128:
+ rc = wqp_soring_init(&lc->wqpool.queue[i].sor, &prm, sz, sid);
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#983: FILE: examples/l3fwd/l3fwd_wqp.c:149:
+ if (prm->mode == L3FWD_WORKER_UNQUE)
WARNING:TYPO_SPELLING: 'unque' may be misspelled - perhaps 'unique'?
#984: FILE: examples/l3fwd/l3fwd_wqp.c:150:
+ return l3fwd_wqp_unque_init(lc, prm, lcid);
WARNING:TYPO_SPELLING: 'paramer' may be misspelled - perhaps 'parameter'?
#1039: FILE: examples/l3fwd/l3fwd_wqp.c:205:
+ printf("error: %s invalid paramer values
", __func__);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1122: FILE: examples/l3fwd/l3fwd_wqp.h:8:
+#include <rte_soring.h>
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#1140: FILE: examples/l3fwd/l3fwd_wqp.h:26:
+ if (wqp->prm.mode == L3FWD_WORKER_UNQUE) {
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1145: FILE: examples/l3fwd/l3fwd_wqp.h:31:
+ struct rte_soring *sor = wqp->queue[idx].sor;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1146: FILE: examples/l3fwd/l3fwd_wqp.h:32:
+ return rte_soring_enqueue_burst(sor, pkts, num, NULL);
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#1164: FILE: examples/l3fwd/l3fwd_wqp.h:50:
+ if (wqp->prm.mode == L3FWD_WORKER_UNQUE) {
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1177: FILE: examples/l3fwd/l3fwd_wqp.h:63:
+ struct rte_soring *sor = wqp->queue[idx].sor;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1179: FILE: examples/l3fwd/l3fwd_wqp.h:65:
+ n = rte_soring_dequeux_burst(sor, pkts, rcs, num, NULL);
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#1196: FILE: examples/l3fwd/l3fwd_wqp.h:82:
+ if (wqp->prm.mode == L3FWD_WORKER_UNQUE) {
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1201: FILE: examples/l3fwd/l3fwd_wqp.h:87:
+ struct rte_soring *sor = wqp->queue[idx].sor;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1202: FILE: examples/l3fwd/l3fwd_wqp.h:88:
+ return rte_soring_acquire_burst(sor, pkts, 0, num,
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#1221: FILE: examples/l3fwd/l3fwd_wqp.h:107:
+ if (wqp->prm.mode == L3FWD_WORKER_UNQUE) {
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1231: FILE: examples/l3fwd/l3fwd_wqp.h:117:
+ struct rte_soring *sor = wqp->queue[idx].sor;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1235: FILE: examples/l3fwd/l3fwd_wqp.h:121:
+ rte_soring_releasx(sor, NULL, rcs, 0, num,
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 8)
#1319: FILE: examples/l3fwd/main.c:612:
+ else
[...]
+ if (strcmp(optarg, "wqorder") == 0) {
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#1325: FILE: examples/l3fwd/main.c:618:
+ l3fwd_wqp_param.mode = L3FWD_WORKER_UNQUE;
WARNING:TYPO_SPELLING: 'UNQUE' may be misspelled - perhaps 'UNIQUE'?
#1331: FILE: examples/l3fwd/main.c:624:
+ l3fwd_wqp_param.mode = L3FWD_WORKER_UNQUE;
total: 0 errors, 33 warnings, 1209 lines checked
next prev parent reply other threads:[~2024-09-06 13:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240906131348.804-7-konstantin.v.ananyev@yandex.ru>
2024-09-06 12:55 ` |SUCCESS| pw143719-143724 " qemudev
2024-09-06 12:59 ` qemudev
2024-09-06 13:16 ` checkpatch [this message]
2024-09-06 14:04 ` |FAILURE| pw143724 " 0-day Robot
2024-09-11 0:48 ` |SUCCESS| pw143719-143724 [PATCH] [RFCv2,6/6] examples/l3fwd: make A dpdklab
2024-09-11 1:34 ` dpdklab
2024-09-11 3:11 ` dpdklab
2024-09-11 5:40 ` |PENDING| " dpdklab
2024-09-11 6:10 ` dpdklab
2024-09-11 6:12 ` dpdklab
2024-09-11 6:23 ` |SUCCESS| " dpdklab
2024-09-11 7:51 ` |WARNING| " dpdklab
2024-09-11 8:52 ` |SUCCESS| " dpdklab
2024-09-11 10:22 ` dpdklab
2024-09-11 10:46 ` |PENDING| " dpdklab
2024-09-11 11:17 ` |FAILURE| " dpdklab
2024-09-11 11:58 ` |WARNING| " dpdklab
2024-09-11 14:18 ` |SUCCESS| " dpdklab
2024-09-11 14:22 ` dpdklab
2024-09-11 14:27 ` dpdklab
2024-09-11 14:31 ` dpdklab
2024-09-11 14:51 ` dpdklab
2024-09-11 15:45 ` |WARNING| " dpdklab
2024-09-11 16:04 ` |SUCCESS| " dpdklab
2024-09-11 19:05 ` dpdklab
2024-09-11 21:20 ` |FAILURE| " dpdklab
2024-09-15 20:23 ` |SUCCESS| " dpdklab
2024-09-16 1:34 ` 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=20240906131600.D0D4E121D10@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--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).