From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw83005 [PATCH v10 13/23] event/dlb: add port setup
Date: Fri, 30 Oct 2020 19:32:04 +0100 (CET) [thread overview]
Message-ID: <20201030183204.763024C89@dpdk.org> (raw)
In-Reply-To: <1604082458-15368-14-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/83005
_coding style issues_
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#241: FILE: drivers/event/dlb/dlb.c:763:
+ cfg.cq_history_list_size = DLB_NUM_HIST_LIST_ENTRIES_PER_LDB_PORT;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#960: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4800:
+ DLB_HW_INFO(hw, " CQ hist list size: %d
",
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1137: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4977:
+ resp->status = DLB_ST_INVALID_HIST_LIST_DEPTH;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1141: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4981:
+ if (args->cq_history_list_size > domain->avail_hist_list_entries) {
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1142: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4982:
+ resp->status = DLB_ST_HIST_LIST_ENTRIES_UNAVAILABLE;
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1171: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5011:
+ union dlb_sys_ldb_pp2vas r3 = { {0} };
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1224: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5064:
+ r3.field.vas = domain->id;
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#1226: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5066:
+ DLB_CSR_WR(hw, DLB_SYS_LDB_PP2VAS(port->id), r3.val);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1305: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5145:
+ union dlb_chp_hist_list_lim r4 = { {0} };
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1306: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5146:
+ union dlb_chp_hist_list_base r5 = { {0} };
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1309: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5149:
+ union dlb_chp_hist_list_push_ptr r8 = { {0} };
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1310: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5150:
+ union dlb_chp_hist_list_pop_ptr r9 = { {0} };
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1388: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5228:
+ r4.field.limit = port->hist_list_entry_limit - 1;
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1390: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5230:
+ DLB_CSR_WR(hw, DLB_CHP_HIST_LIST_LIM(port->id), r4.val);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1392: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5232:
+ r5.field.base = port->hist_list_entry_base;
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1394: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5234:
+ DLB_CSR_WR(hw, DLB_CHP_HIST_LIST_BASE(port->id), r5.val);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1399: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5239:
+ DLB_CSR_WR(hw, DLB_CHP_HIST_LIST_PUSH_PTR(port->id), r8.val);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1404: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5244:
+ DLB_CSR_WR(hw, DLB_CHP_HIST_LIST_POP_PTR(port->id), r9.val);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1463: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5303:
+ port->hist_list_entry_base = domain->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1463: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5303:
+ port->hist_list_entry_base = domain->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1464: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5304:
+ domain->hist_list_entry_offset;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1465: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5305:
+ port->hist_list_entry_limit = port->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1465: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5305:
+ port->hist_list_entry_limit = port->hist_list_entry_base +
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1468: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5308:
+ domain->hist_list_entry_offset += args->cq_history_list_size;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1469: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5309:
+ domain->avail_hist_list_entries -= args->cq_history_list_size;
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1813: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5653:
+ union dlb_sys_dir_pp2vas r3 = { {0} };
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1873: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5713:
+ r3.field.vas = domain->id;
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#1876: FILE: drivers/event/dlb/pf/base/dlb_resource.c:5716:
+ DLB_SYS_DIR_PP2VAS(port->id),
total: 0 errors, 28 warnings, 2308 lines checked
parent reply other threads:[~2020-10-30 18:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1604082458-15368-14-git-send-email-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=20201030183204.763024C89@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).