From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw81228 [PATCH v5 06/22] event/dlb: add probe
Date: Sat, 17 Oct 2020 21:06:28 +0200 (CEST) [thread overview]
Message-ID: <20201017190628.26587CA68@dpdk.org> (raw)
In-Reply-To: <1602961456-17392-7-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/81228
_coding style issues_
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#234: FILE: drivers/event/dlb/dlb.c:124:
+ dlb->hw_rsrc_query_results.num_hist_list_entries;
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#713: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:20:
+#define DLB_MAX_NUM_HIST_LIST_ENTRIES 5120
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#869: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:176:
+ u32 hist_list_entry_base;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#870: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:177:
+ u32 hist_list_entry_limit;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#955: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:262:
+ u32 total_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#956: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:263:
+ u32 avail_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#957: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:264:
+ u32 hist_list_entry_base;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#958: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:265:
+ u32 hist_list_entry_offset;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#981: FILE: drivers/event/dlb/pf/base/dlb_hw_types.h:288:
+ struct dlb_bitmap *avail_hist_list_entries;
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2007: FILE: drivers/event/dlb/pf/base/dlb_regs.h:21:
+#define DLB_SYS_TOTAL_VAS 0x124
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2008: FILE: drivers/event/dlb/pf/base/dlb_regs.h:22:
+#define DLB_SYS_TOTAL_VAS_RST 0x20
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2009: FILE: drivers/event/dlb/pf/base/dlb_regs.h:23:
+union dlb_sys_total_vas {
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2011: FILE: drivers/event/dlb/pf/base/dlb_regs.h:25:
+ u32 total_vas : 32;
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2233: FILE: drivers/event/dlb/pf/base/dlb_regs.h:247:
+#define DLB_SYS_LDB_PP2VAS(x) \
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2235: FILE: drivers/event/dlb/pf/base/dlb_regs.h:249:
+#define DLB_SYS_LDB_PP2VAS_RST 0x0
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2236: FILE: drivers/event/dlb/pf/base/dlb_regs.h:250:
+union dlb_sys_ldb_pp2vas {
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2238: FILE: drivers/event/dlb/pf/base/dlb_regs.h:252:
+ u32 vas : 5;
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2357: FILE: drivers/event/dlb/pf/base/dlb_regs.h:371:
+#define DLB_SYS_DIR_PP2VAS(x) \
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2359: FILE: drivers/event/dlb/pf/base/dlb_regs.h:373:
+#define DLB_SYS_DIR_PP2VAS_RST 0x0
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2360: FILE: drivers/event/dlb/pf/base/dlb_regs.h:374:
+union dlb_sys_dir_pp2vas {
WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2362: FILE: drivers/event/dlb/pf/base/dlb_regs.h:376:
+ u32 vas : 5;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#3564: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1578:
+ u32 en_tim : 1;
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3692: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1706:
+#define DLB_CHP_HIST_LIST_BASE(x) \
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3694: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1708:
+#define DLB_CHP_HIST_LIST_BASE_RST 0x0
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3695: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1709:
+union dlb_chp_hist_list_base {
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3703: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1717:
+#define DLB_CHP_HIST_LIST_LIM(x) \
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3705: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1719:
+#define DLB_CHP_HIST_LIST_LIM_RST 0x0
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3706: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1720:
+union dlb_chp_hist_list_lim {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#3774: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1788:
+ u32 en_tim : 1;
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3990: FILE: drivers/event/dlb/pf/base/dlb_regs.h:2004:
+#define DLB_CHP_HIST_LIST_POP_PTR(x) \
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3992: FILE: drivers/event/dlb/pf/base/dlb_regs.h:2006:
+#define DLB_CHP_HIST_LIST_POP_PTR_RST 0x0
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3993: FILE: drivers/event/dlb/pf/base/dlb_regs.h:2007:
+union dlb_chp_hist_list_pop_ptr {
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#4002: FILE: drivers/event/dlb/pf/base/dlb_regs.h:2016:
+#define DLB_CHP_HIST_LIST_PUSH_PTR(x) \
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#4004: FILE: drivers/event/dlb/pf/base/dlb_regs.h:2018:
+#define DLB_CHP_HIST_LIST_PUSH_PTR_RST 0x0
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4005: FILE: drivers/event/dlb/pf/base/dlb_regs.h:2019:
+union dlb_chp_hist_list_push_ptr {
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4451: FILE: drivers/event/dlb/pf/base/dlb_resource.c:91:
+ map = rsrcs->avail_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4453: FILE: drivers/event/dlb/pf/base/dlb_resource.c:93:
+ arg->num_hist_list_entries = dlb_bitmap_count(map);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4455: FILE: drivers/event/dlb/pf/base/dlb_resource.c:95:
+ arg->max_contiguous_hist_list_entries =
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4581: FILE: drivers/event/dlb/pf/base/dlb_resource.c:221:
+ &hw->pf.avail_hist_list_entries,
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#4582: FILE: drivers/event/dlb/pf/base/dlb_resource.c:222:
+ DLB_MAX_NUM_HIST_LIST_ENTRIES))
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4585: FILE: drivers/event/dlb/pf/base/dlb_resource.c:225:
+ if (dlb_bitmap_fill(hw->pf.avail_hist_list_entries))
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4644: FILE: drivers/event/dlb/pf/base/dlb_resource.c:284:
+ dlb_bitmap_free(hw->pf.avail_hist_list_entries);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5373: FILE: drivers/event/dlb/pf/base/dlb_resource.h:705:
+ * - max_contiguous_hist_list_entries
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#5381: FILE: drivers/event/dlb/pf/base/dlb_resource.h:713:
+ * dlb_disable_dp_vasr_feature() - disable directed pipe VAS reset hardware
WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#5385: FILE: drivers/event/dlb/pf/base/dlb_resource.h:717:
+ * necessary to workaround a DLB VAS reset issue.
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#6260: FILE: drivers/event/dlb/pf/dlb_pf.c:55:
+ dlb_port[i][DLB_DIR].mmaped = true;
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#6273: FILE: drivers/event/dlb/pf/dlb_pf.c:68:
+ dlb_port[i][DLB_LDB].mmaped = true;
total: 0 errors, 47 warnings, 6239 lines checked
parent reply other threads:[~2020-10-17 19:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1602961456-17392-7-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=20201017190628.26587CA68@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).