From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw91304 [PATCH v3 05/26] event/dlb2: add v2.5 create sched domain
Date: Tue, 13 Apr 2021 22:18:53 +0200 (CEST) [thread overview]
Message-ID: <20210413201853.A8CCF1209EC@dpdk.org> (raw)
In-Reply-To: <1618344896-2090-6-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/91304
_coding style issues_
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#785: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:332:
+ DLB2_BITS_SET(reg, domain->num_credits, DLB2_CHP_CFG_LDB_VAS_CRD_COUNT);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#786: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:333:
+ DLB2_CSR_WR(hw, DLB2_CHP_CFG_VAS_CRD(domain->id.phys_id), reg);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#795: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:342:
+ DLB2_CHP_CFG_LDB_VAS_CRD_COUNT);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#796: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:343:
+ DLB2_CSR_WR(hw, DLB2_CHP_CFG_LDB_VAS_CRD(domain->id.phys_id), reg);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#800: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:347:
+ DLB2_CHP_CFG_DIR_VAS_CRD_COUNT);
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#801: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:348:
+ DLB2_CSR_WR(hw, DLB2_CHP_CFG_DIR_VAS_CRD(domain->id.phys_id), reg);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1121: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:668:
+dlb2_attach_domain_hist_list_entries(struct dlb2_function_resources *rsrcs,
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1123: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:670:
+ u32 num_hist_list_entries,
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1129: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:676:
+ if (num_hist_list_entries) {
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1130: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:677:
+ bitmap = rsrcs->avail_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1133: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:680:
+ num_hist_list_entries);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1137: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:684:
+ domain->total_hist_list_entries = num_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1137: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:684:
+ domain->total_hist_list_entries = num_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1138: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:685:
+ domain->avail_hist_list_entries = num_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1138: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:685:
+ domain->avail_hist_list_entries = num_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1139: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:686:
+ domain->hist_list_entry_base = base;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1140: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:687:
+ domain->hist_list_entry_offset = 0;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1142: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:689:
+ dlb2_bitmap_clear_range(bitmap, base, num_hist_list_entries);
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1147: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:694:
+ resp->status = DLB2_ST_HIST_LIST_ENTRIES_UNAVAILABLE;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1245: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:792:
+ ret = dlb2_attach_domain_hist_list_entries(rsrcs,
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1247: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:794:
+ args->num_hist_list_entries,
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1283: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:830:
+ avail_hl_entries = rsrcs->avail_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1356: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:903:
+ if (max_contig_hl_range < args->num_hist_list_entries) {
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1357: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:904:
+ resp->status = DLB2_ST_HIST_LIST_ENTRIES_UNAVAILABLE;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1393: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:940:
+ DLB2_HW_DBG(hw, " Number of hist list entries: %d
",
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1394: FILE: drivers/event/dlb2/pf/base/dlb2_resource_new.c:941:
+ args->num_hist_list_entries);
total: 0 errors, 26 warnings, 1387 lines checked
parent reply other threads:[~2021-04-13 20:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1618344896-2090-6-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=20210413201853.A8CCF1209EC@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).