From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sun Yuechi <sunyuechi@iscas.ac.cn>
Subject: |WARNING| pw159505 [PATCH v2] acl: add RISC-V vector extension implementation
Date: Mon, 29 Dec 2025 06:47:03 +0100 (CET) [thread overview]
Message-ID: <20251229054703.DF1BF124270@dpdk.org> (raw)
In-Reply-To: <20251229054559.2923969-1-sunyuechi@iscas.ac.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159505
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#221: FILE: lib/acl/acl_run_rvv.h:21:
+ struct parms *parms, const struct rte_acl_match_results *p,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#221: FILE: lib/acl/acl_run_rvv.h:21:
+ struct parms *parms, const struct rte_acl_match_results *p,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#235: FILE: lib/acl/acl_run_rvv.h:35:
+ if (parms[n].cmplt->count != ctx->num_tries) {
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#239: FILE: lib/acl/acl_run_rvv.h:39:
+ __riscv_vle32_v_u32m1(&parms[n].cmplt->results[i], vl);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#241: FILE: lib/acl/acl_run_rvv.h:41:
+ __riscv_vle32_v_i32m1(&parms[n].cmplt->priority[i], vl);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#254: FILE: lib/acl/acl_run_rvv.h:54:
+ __riscv_vse32_v_u32m1(&parms[n].cmplt->results[i],
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#256: FILE: lib/acl/acl_run_rvv.h:56:
+ __riscv_vse32_v_i32m1(&parms[n].cmplt->priority[i],
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#266: FILE: lib/acl/acl_run_rvv.h:66:
+ const struct rte_acl_ctx *ctx, struct parms *parms,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#266: FILE: lib/acl/acl_run_rvv.h:66:
+ const struct rte_acl_ctx *ctx, struct parms *parms,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#271: FILE: lib/acl/acl_run_rvv.h:71:
+ parms, flows, resolve_priority_rvv);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#275: FILE: lib/acl/acl_run_rvv.h:75:
+ parms, flows, resolve_priority_rvv);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#283: FILE: lib/acl/acl_run_rvv.h:83:
+ struct parms *parms, struct acl_flow_data *flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#283: FILE: lib/acl/acl_run_rvv.h:83:
+ struct parms *parms, struct acl_flow_data *flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#295: FILE: lib/acl/acl_run_rvv.h:95:
+ acl_process_matches(indices1, slot, ctx, parms, flows);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#296: FILE: lib/acl/acl_run_rvv.h:96:
+ acl_process_matches(indices2, slot + 2, ctx, parms, flows);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#396: FILE: lib/acl/acl_run_rvv.h:196:
+ struct parms parms[MAX_SEARCHES_RVV8];
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#406: FILE: lib/acl/acl_run_rvv.h:206:
+ index_array[n] = acl_start_next_trie(&flows, parms, n, ctx);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#414: FILE: lib/acl/acl_run_rvv.h:214:
+ acl_match_check_x4(0, ctx, parms, &flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#416: FILE: lib/acl/acl_run_rvv.h:216:
+ acl_match_check_x4(4, ctx, parms, &flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#423: FILE: lib/acl/acl_run_rvv.h:223:
+ GET_NEXT_4BYTES(parms, 0),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#424: FILE: lib/acl/acl_run_rvv.h:224:
+ GET_NEXT_4BYTES(parms, 1),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#425: FILE: lib/acl/acl_run_rvv.h:225:
+ GET_NEXT_4BYTES(parms, 2),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#426: FILE: lib/acl/acl_run_rvv.h:226:
+ GET_NEXT_4BYTES(parms, 3)
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#429: FILE: lib/acl/acl_run_rvv.h:229:
+ GET_NEXT_4BYTES(parms, 4),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#430: FILE: lib/acl/acl_run_rvv.h:230:
+ GET_NEXT_4BYTES(parms, 5),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#431: FILE: lib/acl/acl_run_rvv.h:231:
+ GET_NEXT_4BYTES(parms, 6),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#432: FILE: lib/acl/acl_run_rvv.h:232:
+ GET_NEXT_4BYTES(parms, 7)
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#461: FILE: lib/acl/acl_run_rvv.h:261:
+ acl_match_check_x4(0, ctx, parms, &flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#463: FILE: lib/acl/acl_run_rvv.h:263:
+ acl_match_check_x4(4, ctx, parms, &flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#482: FILE: lib/acl/acl_run_rvv.h:282:
+ struct parms parms[MAX_SEARCHES_RVV4];
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#492: FILE: lib/acl/acl_run_rvv.h:292:
+ index_array[n] = acl_start_next_trie(&flows, parms, n, ctx);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#495: FILE: lib/acl/acl_run_rvv.h:295:
+ acl_match_check_x4(0, ctx, parms, &flows,
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#502: FILE: lib/acl/acl_run_rvv.h:302:
+ GET_NEXT_4BYTES(parms, 0),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#503: FILE: lib/acl/acl_run_rvv.h:303:
+ GET_NEXT_4BYTES(parms, 1),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#504: FILE: lib/acl/acl_run_rvv.h:304:
+ GET_NEXT_4BYTES(parms, 2),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#505: FILE: lib/acl/acl_run_rvv.h:305:
+ GET_NEXT_4BYTES(parms, 3)
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#521: FILE: lib/acl/acl_run_rvv.h:321:
+ acl_match_check_x4(0, ctx, parms, &flows,
^^^^^
total: 0 errors, 37 warnings, 483 lines checked
next parent reply other threads:[~2025-12-29 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251229054559.2923969-1-sunyuechi@iscas.ac.cn>
2025-12-29 5:47 ` checkpatch [this message]
2025-12-29 6:01 ` |SUCCESS| " qemudev
2025-12-29 6:06 ` qemudev
2025-12-29 7:23 ` 0-day Robot
2025-12-29 7:23 ` 0-day Robot
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=20251229054703.DF1BF124270@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sunyuechi@iscas.ac.cn \
--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).