From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Subject: |WARNING| pw144519 [PATCH v2 26/47] net/bnxt: tf_ulp: enable recipe id generation
Date: Sat, 28 Sep 2024 00:28:27 +0200 (CEST) [thread overview]
Message-ID: <20240927222827.C754D121D9E@dpdk.org> (raw)
In-Reply-To: <20240927180829.525350-27-sriharsha.basavapatna@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/144519
_coding style issues_
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#395: 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'?
#415: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1767:
+ mdata = ulp_mapper_key_recipe_args_validate(parms->ulp_ctx, dir,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#445: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1797:
+ rc = ulp_regfile_write(parms->regfile, tbl->tbl_operand,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#457: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1809:
+ recipe = ulp_mapper_key_recipe_alloc(parms->ulp_ctx, dir, stype,
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#476: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1821:
+ kflds = ulp_mapper_key_fields_get(parms, tbl, &num_kflds);
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#524: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1854:
+ rc = ulp_mapper_key_recipe_field_opc_process(parms,
total: 0 errors, 6 warnings, 0 checks, 422 lines checked
parent reply other threads:[~2024-09-27 22:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240927180829.525350-27-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=20240927222827.C754D121D9E@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).