automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: |WARNING| pw148067 [PATCH v8 47/47] net/bnxt: tf_ulp: add stats cache for thor2
Date: Thu,  7 Nov 2024 15:12:28 +0100 (CET)	[thread overview]
Message-ID: <20241107141228.7F6E812314F@dpdk.org> (raw)
In-Reply-To: <20241107135254.1611676-48-sriharsha.basavapatna@broadcom.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148067

_coding style issues_


WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#513: 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'?
#513: 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'?
#516: 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'?
#531: 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'?
#542: 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'?
#542: 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'?
#543: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2984:
+	fid_parms.direction	= tbl->direction;

WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#544: 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'?
#545: 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'?
#546: 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'?
#547: 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'?
#548: 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'?
#549: 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'?
#549: 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'?
#556: 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'?
#564: 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'?
#586: 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'?
#680: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:73:
+		BNXT_DRV_DBG(DEBUG, "Failed to device parms
");

CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#950: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:343:
+					 "Stats collection time exceeded %dmS Cycles:%" PRIu64,

WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1076: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:469:
+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.c:469:
+int ulp_sc_mgr_entry_alloc(struct bnxt_ulp_mapper_parms *parms,

WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1083: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:476:
+	ulp_sc_info = bnxt_ulp_cntxt_ptr2_sc_info_get(parms->ulp_ctx);

WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1090: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:483:
+	sce += parms->flow_id;

WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1099: FILE: drivers/net/bnxt/tf_ulp/ulp_sc_mgr.c:492:
+	sce->ctxt = parms->ulp_ctx;

WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#1260: 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'?
#1265: 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'?
#1265: 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, 1 checks, 1139 lines checked

       reply	other threads:[~2024-11-07 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241107135254.1611676-48-sriharsha.basavapatna@broadcom.com>
2024-11-07 14:12 ` checkpatch [this message]
2024-11-07 15:32 ` |SUCCESS| " 0-day Robot
2024-11-07 16:19 ` |SUCCESS| pw148034-148067 " qemudev
2024-11-07 16:23 ` qemudev
2024-11-07 18:43 ` |SUCCESS| pw148034-148067 [PATCH] [v8,47/47] net/bnxt: tf_ulp: add s dpdklab
2024-11-07 18:49 ` dpdklab
2024-11-07 18:50 ` dpdklab
2024-11-07 18:55 ` dpdklab
2024-11-07 18:58 ` |PENDING| " 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=20241107141228.7F6E812314F@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).