From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: |WARNING| pw148054 [PATCH v8 28/47] net/bnxt: tf_ulp: modify return values to adhere to C coding standard
Date: Thu, 7 Nov 2024 15:20:51 +0100 (CET) [thread overview]
Message-ID: <20241107142051.7082412314F@dpdk.org> (raw)
In-Reply-To: <20241107135254.1611676-29-sriharsha.basavapatna@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148054
_coding style issues_
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#124: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:633:
+ if (ulp_regfile_read(parms->regfile, tbl->pri_operand,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#155: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:907:
+ if (ulp_regfile_read(parms->regfile, idx, &lregval) ||
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#350: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1537:
+ if (ulp_regfile_read(parms->regfile, tbl->key_recipe_operand,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#373: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1752:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#388: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2167:
+ parms->device_params->encap_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#399: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2279:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#412: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2324:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#438: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2565:
+ parms->device_params->key_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#478: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3216:
+ if (ulp_regfile_read(parms->regfile, operand, ®val)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#487: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3225:
+ if (ulp_regfile_read(parms->regfile, operand, ®val)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#496: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3372:
+ if (ulp_regfile_read(parms->regfile, func_opr, ®val)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#533: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3941:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#546: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:3955:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#558: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:4114:
+ if (ulp_regfile_read(parms->regfile, rf_idx,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#568: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:4367:
+ if (ulp_regfile_init(parms->regfile)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#613: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tf.c:630:
+ parms->device_params->result_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#624: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tf.c:659:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#636: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tf.c:724:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#648: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tf.c:951:
+ parms->device_params->result_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#657: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tf.c:969:
+ if (ulp_regfile_read(parms->regfile, tbl->tbl_operand, &idx)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#668: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tf.c:982:
+ parms->device_params->result_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#716: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:784:
+ parms->device_params->result_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#726: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:849:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#738: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:897:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#751: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:1097:
+ parms->device_params->result_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#761: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:1162:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#773: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:1183:
+ if (ulp_regfile_read(parms->regfile,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#786: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:1453:
+ parms->device_params->result_byte_order)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#795: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:1471:
+ if (ulp_regfile_read(parms->regfile, tbl->tbl_operand, &idx)) {
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#806: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:1484:
+ parms->device_params->result_byte_order)) {
total: 0 errors, 30 warnings, 0 checks, 914 lines checked
parent reply other threads:[~2024-11-07 14:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241107135254.1611676-29-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=20241107142051.7082412314F@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).