From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: |WARNING| pw148066 [PATCH v8 45/47] net/bnxt: tf_ulp: support a few feature extensions
Date: Thu, 7 Nov 2024 15:13:37 +0100 (CET) [thread overview]
Message-ID: <20241107141337.83CBE12314F@dpdk.org> (raw)
In-Reply-To: <20241107135254.1611676-46-sriharsha.basavapatna@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148066
_coding style issues_
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#385: FILE: drivers/net/bnxt/tf_ulp/ulp_def_rules.c:765:
+ struct bnxt_ulp_mapper_parms mapper_params = { 0 };
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#500: FILE: drivers/net/bnxt/tf_ulp/ulp_def_rules.c:880:
+ struct bnxt_ulp_mapper_parms mparms = { 0 };
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#625: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:862:
+ulp_mapper_field_port_db_write(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#625: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:862:
+ulp_mapper_field_port_db_write(struct bnxt_ulp_mapper_parms *parms,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#641: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:878:
+ if (unlikely(ulp_port_db_port_table_mirror_set(parms->ulp_ctx,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#674: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3719:
+ rc = ulp_mapper_field_port_db_write(parms, res1,
total: 0 errors, 6 warnings, 0 checks, 684 lines checked
parent reply other threads:[~2024-11-07 14:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241107135254.1611676-46-sriharsha.basavapatna@broadcom.com>]
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=20241107141337.83CBE12314F@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).