|WARNING| pw160665 [PATCH v3] acl: add RISC-V vector extension implementation
checkpatch at dpdk.org
checkpatch at dpdk.org
Sun Feb 1 20:13:56 CET 2026
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/160665
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#241: 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'?
#241: 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'?
#255: 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'?
#259: 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'?
#261: 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'?
#274: 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'?
#276: 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'?
#286: 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'?
#286: 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'?
#291: FILE: lib/acl/acl_run_rvv.h:71:
+ parms, flows, resolve_priority_rvv);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#295: FILE: lib/acl/acl_run_rvv.h:75:
+ parms, flows, resolve_priority_rvv);
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#303: 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'?
#303: 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'?
#315: 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'?
#316: 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'?
#416: FILE: lib/acl/acl_run_rvv.h:196:
+ struct parms parms[MAX_SEARCHES_RVV8];
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#426: 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'?
#434: 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'?
#436: 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'?
#443: FILE: lib/acl/acl_run_rvv.h:223:
+ GET_NEXT_4BYTES(parms, 0),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#444: FILE: lib/acl/acl_run_rvv.h:224:
+ GET_NEXT_4BYTES(parms, 1),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#445: FILE: lib/acl/acl_run_rvv.h:225:
+ GET_NEXT_4BYTES(parms, 2),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#446: FILE: lib/acl/acl_run_rvv.h:226:
+ GET_NEXT_4BYTES(parms, 3)
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#449: FILE: lib/acl/acl_run_rvv.h:229:
+ GET_NEXT_4BYTES(parms, 4),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#450: FILE: lib/acl/acl_run_rvv.h:230:
+ GET_NEXT_4BYTES(parms, 5),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#451: FILE: lib/acl/acl_run_rvv.h:231:
+ GET_NEXT_4BYTES(parms, 6),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#452: FILE: lib/acl/acl_run_rvv.h:232:
+ GET_NEXT_4BYTES(parms, 7)
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#481: 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'?
#483: 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'?
#502: FILE: lib/acl/acl_run_rvv.h:282:
+ struct parms parms[MAX_SEARCHES_RVV4];
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#512: 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'?
#515: 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'?
#522: FILE: lib/acl/acl_run_rvv.h:302:
+ GET_NEXT_4BYTES(parms, 0),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#523: FILE: lib/acl/acl_run_rvv.h:303:
+ GET_NEXT_4BYTES(parms, 1),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#524: FILE: lib/acl/acl_run_rvv.h:304:
+ GET_NEXT_4BYTES(parms, 2),
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#525: FILE: lib/acl/acl_run_rvv.h:305:
+ GET_NEXT_4BYTES(parms, 3)
^^^^^
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#541: FILE: lib/acl/acl_run_rvv.h:321:
+ acl_match_check_x4(0, ctx, parms, &flows,
^^^^^
total: 0 errors, 37 warnings, 495 lines checked
More information about the test-report
mailing list