automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw77490 [PATCH v4 06/22] event/dlb: add probe
Date: Fri, 11 Sep 2020 21:25:10 +0200 (CEST)	[thread overview]
Message-ID: <20200911192510.3B7761C1D5@dpdk.org> (raw)
In-Reply-To: <1599851920-16802-7-git-send-email-timothy.mcdaniel@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/77490

_coding style issues_


WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#227: FILE: drivers/event/dlb/dlb.c:125:
+		dlb->hw_rsrc_query_results.num_hist_list_entries;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#766: 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'?
#922: 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'?
#923: 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'?
#1008: 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'?
#1009: 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'?
#1010: 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'?
#1011: 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'?
#1034: 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'?
#2060: 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'?
#2061: 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'?
#2062: FILE: drivers/event/dlb/pf/base/dlb_regs.h:23:
+union dlb_sys_total_vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2064: FILE: drivers/event/dlb/pf/base/dlb_regs.h:25:
+		u32 total_vas : 32;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2286: 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'?
#2288: 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'?
#2289: FILE: drivers/event/dlb/pf/base/dlb_regs.h:250:
+union dlb_sys_ldb_pp2vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2291: FILE: drivers/event/dlb/pf/base/dlb_regs.h:252:
+		u32 vas : 5;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2410: 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'?
#2412: 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'?
#2413: FILE: drivers/event/dlb/pf/base/dlb_regs.h:374:
+union dlb_sys_dir_pp2vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2415: FILE: drivers/event/dlb/pf/base/dlb_regs.h:376:
+		u32 vas : 5;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#3617: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1578:
+		u32 en_tim : 1;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3745: 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'?
#3747: 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'?
#3748: 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'?
#3756: 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'?
#3758: 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'?
#3759: 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'?
#3827: FILE: drivers/event/dlb/pf/base/dlb_regs.h:1788:
+		u32 en_tim : 1;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#4043: 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'?
#4045: 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'?
#4046: 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'?
#4055: 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'?
#4057: 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'?
#4058: 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'?
#4504: 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'?
#4506: 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'?
#4508: 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'?
#4634: 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'?
#4635: 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'?
#4638: 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'?
#4697: 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'?
#5426: FILE: drivers/event/dlb/pf/base/dlb_resource.h:705:
+ * - max_contiguous_hist_list_entries

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#5434: 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'?
#5438: 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'?
#6313: 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'?
#6326: FILE: drivers/event/dlb/pf/dlb_pf.c:68:
+		dlb_port[i][DLB_LDB].mmaped = true;

total: 0 errors, 47 warnings, 6299 lines checked

           reply	other threads:[~2020-09-11 19:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1599851920-16802-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=20200911192510.3B7761C1D5@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).