From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw89284 [PATCH 07/25] event/dlb2: add DLB v2.5 support to create ldb port
Date: Tue, 16 Mar 2021 23:22:33 +0100 (CET) [thread overview]
Message-ID: <20210316222233.BD5FE2BE3@dpdk.org> (raw)
In-Reply-To: <20210316221857.2254-8-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89284
_coding style issues_
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#590: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:3985:
+ DLB2_BITS_SET(reg, domain->id.phys_id, DLB2_SYS_LDB_PP2VAS_VAS);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#591: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:3986:
+ DLB2_CSR_WR(hw, DLB2_SYS_LDB_PP2VAS(port->id.phys_id), reg);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#731: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4126:
+ port->hist_list_entry_limit - 1,
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#732: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4127:
+ DLB2_CHP_HIST_LIST_LIM_LIMIT);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#733: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4128:
+ DLB2_CSR_WR(hw, DLB2_CHP_HIST_LIST_LIM(hw->ver, port->id.phys_id), reg);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#735: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4130:
+ DLB2_BITS_SET(hl_base, port->hist_list_entry_base,
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#736: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4131:
+ DLB2_CHP_HIST_LIST_BASE_BASE);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#738: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4133:
+ DLB2_CHP_HIST_LIST_BASE(hw->ver, port->id.phys_id),
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#752: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4147:
+ DLB2_BITS_SET(reg, DLB2_BITS_GET(hl_base, DLB2_CHP_HIST_LIST_BASE_BASE),
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#753: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4148:
+ DLB2_CHP_HIST_LIST_PUSH_PTR_PUSH_PTR);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#754: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4149:
+ DLB2_CSR_WR(hw, DLB2_CHP_HIST_LIST_PUSH_PTR(hw->ver, port->id.phys_id),
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#758: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4153:
+ DLB2_BITS_SET(reg, DLB2_BITS_GET(hl_base, DLB2_CHP_HIST_LIST_BASE_BASE),
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#759: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4154:
+ DLB2_CHP_HIST_LIST_POP_PTR_POP_PTR);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#760: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4155:
+ DLB2_CSR_WR(hw, DLB2_CHP_HIST_LIST_POP_PTR(hw->ver, port->id.phys_id),
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#783: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4178:
+ DLB2_BITS_SET(reg, domain->id.phys_id, DLB2_CHP_LDB_CQ2VAS_CQ2VAS);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#783: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4178:
+ DLB2_BITS_SET(reg, domain->id.phys_id, DLB2_CHP_LDB_CQ2VAS_CQ2VAS);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#784: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4179:
+ DLB2_CSR_WR(hw, DLB2_CHP_LDB_CQ2VAS(hw->ver, port->id.phys_id), reg);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#817: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4212:
+ port->hist_list_entry_base = domain->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#817: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4212:
+ port->hist_list_entry_base = domain->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#818: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4213:
+ domain->hist_list_entry_offset;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#819: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4214:
+ port->hist_list_entry_limit = port->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#819: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4214:
+ port->hist_list_entry_limit = port->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#822: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4217:
+ domain->hist_list_entry_offset += args->cq_history_list_size;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#823: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4218:
+ domain->avail_hist_list_entries -= args->cq_history_list_size;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#869: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4264:
+ DLB2_HW_DBG(hw, " CQ hist list size: %d
",
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#949: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4344:
+ resp->status = DLB2_ST_INVALID_HIST_LIST_DEPTH;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#953: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4348:
+ if (args->cq_history_list_size > domain->avail_hist_list_entries) {
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#954: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:4349:
+ resp->status = DLB2_ST_HIST_LIST_ENTRIES_UNAVAILABLE;
total: 0 errors, 28 warnings, 970 lines checked
parent reply other threads:[~2021-03-16 22:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210316221857.2254-8-timothy.mcdaniel@intel.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=20210316222233.BD5FE2BE3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=timothy.mcdaniel@intel.com \
/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).