From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: |WARNING| pw143498 [PATCH 47/47] net/bnxt: tf_ulp: add stats cache for thor2
Date: Fri, 30 Aug 2024 16:11:13 +0200 (CEST) [thread overview]
Message-ID: <20240830141113.335F1120778@dpdk.org> (raw)
In-Reply-To: <20240830140049.1715230-48-sriharsha.basavapatna@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143498
_coding style issues_
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#321: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2954:
+ulp_mapper_stats_cache_tbl_process(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#321: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2954:
+ulp_mapper_stats_cache_tbl_process(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#324: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2957:
+ struct ulp_flow_db_res_params fid_parms;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#339: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2972:
+ rc = ulp_mapper_tbl_result_build(parms, tbl, &data,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#350: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2983:
+ memset(&fid_parms, 0, sizeof(fid_parms));
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#350: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2983:
+ memset(&fid_parms, 0, sizeof(fid_parms));
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#351: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2984:
+ fid_parms.direction = tbl->direction;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#352: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2985:
+ fid_parms.resource_func = tbl->resource_func;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#353: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2986:
+ fid_parms.resource_type = tbl->resource_type;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#354: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2987:
+ fid_parms.resource_sub_type = tbl->resource_sub_type;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#355: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2988:
+ fid_parms.resource_hndl = counter_handle;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#356: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2989:
+ fid_parms.critical_resource = tbl->critical_resource;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#357: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2990:
+ rc = ulp_mapper_fdb_opc_process(parms, tbl, &fid_parms);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#357: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2990:
+ rc = ulp_mapper_fdb_opc_process(parms, tbl, &fid_parms);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#364: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2997:
+ rc = ulp_sc_mgr_entry_alloc(parms, counter_handle, tbl);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#372: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3005:
+ BNXT_DRV_DBG(DEBUG, "flow id =0x%x
", parms->flow_id);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#394: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:4218:
+ rc = ulp_mapper_stats_cache_tbl_process(parms, tbl);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#488: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:73:
+ BNXT_DRV_DBG(DEBUG, "Failed to device parms
");
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#887: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:472:
+int ulp_sc_mgr_entry_alloc(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#887: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:472:
+int ulp_sc_mgr_entry_alloc(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#894: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:479:
+ ulp_sc_info = bnxt_ulp_cntxt_ptr2_sc_info_get(parms->ulp_ctx);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#901: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:486:
+ sce += parms->flow_id;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#910: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:495:
+ sce->ctxt = parms->ulp_ctx;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1071: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.h:121:
+ * parms [in] Various fields used to identify the flow
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1076: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.h:126:
+int ulp_sc_mgr_entry_alloc(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1076: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.h:126:
+int ulp_sc_mgr_entry_alloc(struct bnxt_ulp_mapper_parms *parms,
total: 0 errors, 26 warnings, 0 checks, 974 lines checked
Warning in drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:
Using %l format, prefer %PRI*64 if type is [u]int64_t
Warning in drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:
Using pthread functions, prefer rte_thread
next parent reply other threads:[~2024-08-30 14:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240830140049.1715230-48-sriharsha.basavapatna@broadcom.com>
2024-08-30 14:11 ` checkpatch [this message]
2024-08-30 14:39 ` |SUCCESS| pw143465-143498 [PATCH] [47/47] net/bnxt: tf_ulp: add stat dpdklab
2024-08-30 14:40 ` |PENDING| " dpdklab
2024-08-30 14:45 ` dpdklab
2024-08-30 14:48 ` dpdklab
2024-08-30 14:49 ` |SUCCESS| " dpdklab
2024-08-30 14:55 ` |SUCCESS| pw143465-143498 [PATCH 47/47] net/bnxt: tf_ulp: add stats cache for thor2 qemudev
2024-08-30 14:59 ` |PENDING| pw143465-143498 [PATCH] [47/47] net/bnxt: tf_ulp: add stat dpdklab
2024-08-30 14:59 ` |SUCCESS| pw143465-143498 [PATCH 47/47] net/bnxt: tf_ulp: add stats cache for thor2 qemudev
2024-08-30 15:04 ` |FAILURE| pw143498 " 0-day Robot
2024-08-30 15:11 ` |SUCCESS| pw143465-143498 [PATCH] [47/47] net/bnxt: tf_ulp: add stat dpdklab
2024-08-30 15:14 ` |FAILURE| " dpdklab
2024-08-30 15:15 ` dpdklab
2024-08-30 15:15 ` dpdklab
2024-08-30 15:15 ` |SUCCESS| " dpdklab
2024-08-30 15:15 ` |FAILURE| " dpdklab
2024-08-30 15:16 ` |SUCCESS| " dpdklab
2024-08-30 15:16 ` dpdklab
2024-08-30 15:16 ` dpdklab
2024-08-30 15:17 ` dpdklab
2024-08-30 15:20 ` |FAILURE| " dpdklab
2024-08-30 15:26 ` |WARNING| " dpdklab
2024-08-30 15:27 ` dpdklab
2024-08-30 15:29 ` |SUCCESS| " dpdklab
2024-08-30 15:36 ` dpdklab
2024-08-30 15:39 ` |WARNING| " dpdklab
2024-08-30 15:46 ` |FAILURE| " dpdklab
2024-09-19 6:03 ` |SUCCESS| " dpdklab
2024-09-19 6:22 ` 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=20240830141113.335F1120778@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sriharsha.basavapatna@broadcom.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).