[dpdk-test-report] |WARNING| pw81204 [PATCH v2 06/22] event/dlb2: add probe

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| pw81204 [PATCH v2 06/22] event/dlb2: add probe
Date: Sat, 17 Oct 2020 20:23:54 +0200 (CEST)	[thread overview]
Message-ID: <20201017182354.65A5DCA6E@dpdk.org> (raw)
In-Reply-To: <1602958879-8558-7-git-send-email-timothy.mcdaniel@intel.com>

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

_coding style issues_


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

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#757: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:21:
+#define DLB2_MAX_NUM_HIST_LIST_ENTRIES		2048

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#944: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:208:
+	u32 hist_list_entry_base;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#945: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:209:
+	u32 hist_list_entry_limit;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1014: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:278:
+	u32 total_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1015: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:279:
+	u32 avail_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1016: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:280:
+	u32 hist_list_entry_base;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1017: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:281:
+	u32 hist_list_entry_offset;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1037: FILE: drivers/event/dlb2/pf/base/dlb2_hw_types.h:301:
+	struct dlb2_bitmap *avail_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1314: FILE: drivers/event/dlb2/pf/base/dlb2_mbox.h:205:
+	u32 num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1315: FILE: drivers/event/dlb2/pf/base/dlb2_mbox.h:206:
+	u32 max_contiguous_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1327: FILE: drivers/event/dlb2/pf/base/dlb2_mbox.h:218:
+	u32 num_hist_list_entries;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2753: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:169:
+#define DLB2_SYS_TOTAL_VAS 0x1000011c

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2754: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:170:
+#define DLB2_SYS_TOTAL_VAS_RST 0x20

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2755: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:171:
+union dlb2_sys_total_vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#2757: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:173:
+		u32 total_vas : 32;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3195: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:611:
+#define DLB2_SYS_LDB_PP2VAS(x) \

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3197: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:613:
+#define DLB2_SYS_LDB_PP2VAS_RST 0x0

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3198: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:614:
+union dlb2_sys_ldb_pp2vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3200: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:616:
+		u32 vas : 5;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3333: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:749:
+#define DLB2_SYS_DIR_PP2VAS(x) \

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3335: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:751:
+#define DLB2_SYS_DIR_PP2VAS_RST 0x0

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3336: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:752:
+union dlb2_sys_dir_pp2vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3338: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:754:
+		u32 vas : 5;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3682: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1098:
+#define DLB2_CHP_CFG_DIR_VAS_CRD(x) \

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3684: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1100:
+#define DLB2_CHP_CFG_DIR_VAS_CRD_RST 0x0

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3685: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1101:
+union dlb2_chp_cfg_dir_vas_crd {

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3693: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1109:
+#define DLB2_CHP_CFG_LDB_VAS_CRD(x) \

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3695: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1111:
+#define DLB2_CHP_CFG_LDB_VAS_CRD_RST 0x0

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3696: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1112:
+union dlb2_chp_cfg_ldb_vas_crd {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#3768: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1184:
+		u32 en_tim : 1;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3820: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1236:
+#define DLB2_CHP_DIR_CQ2VAS(x) \

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3822: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1238:
+#define DLB2_CHP_DIR_CQ2VAS_RST 0x0

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3823: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1239:
+union dlb2_chp_dir_cq2vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3825: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1241:
+		u32 cq2vas : 5;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3831: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1247:
+#define DLB2_CHP_HIST_LIST_BASE(x) \

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3833: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1249:
+#define DLB2_CHP_HIST_LIST_BASE_RST 0x0

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3834: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1250:
+union dlb2_chp_hist_list_base {

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3842: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1258:
+#define DLB2_CHP_HIST_LIST_LIM(x) \

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3844: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1260:
+#define DLB2_CHP_HIST_LIST_LIM_RST 0x0

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3845: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1261:
+union dlb2_chp_hist_list_lim {

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3853: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1269:
+#define DLB2_CHP_HIST_LIST_POP_PTR(x) \

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3855: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1271:
+#define DLB2_CHP_HIST_LIST_POP_PTR_RST 0x0

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3856: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1272:
+union dlb2_chp_hist_list_pop_ptr {

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3865: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1281:
+#define DLB2_CHP_HIST_LIST_PUSH_PTR(x) \

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3867: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1283:
+#define DLB2_CHP_HIST_LIST_PUSH_PTR_RST 0x0

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3868: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1284:
+union dlb2_chp_hist_list_push_ptr {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#3904: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1320:
+		u32 en_tim : 1;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3956: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1372:
+#define DLB2_CHP_LDB_CQ2VAS(x) \

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3958: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1374:
+#define DLB2_CHP_LDB_CQ2VAS_RST 0x0

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3959: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1375:
+union dlb2_chp_ldb_cq2vas {

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#3961: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1377:
+		u32 cq2vas : 5;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5205: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:88:
+	map = rsrcs->avail_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5207: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:90:
+	arg->num_hist_list_entries = dlb2_bitmap_count(map);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5209: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:92:
+	arg->max_contiguous_hist_list_entries =

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5234: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:117:
+	if (hw->pf.avail_hist_list_entries)

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5235: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:118:
+		dlb2_bitmap_free(hw->pf.avail_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5238: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:121:
+		if (hw->vdev[i].avail_hist_list_entries)

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5239: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:122:
+			dlb2_bitmap_free(hw->vdev[i].avail_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5322: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:205:
+	ret = dlb2_bitmap_alloc(&hw->pf.avail_hist_list_entries,

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#5323: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:206:
+				DLB2_MAX_NUM_HIST_LIST_ENTRIES);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5327: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:210:
+	ret = dlb2_bitmap_fill(hw->pf.avail_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5332: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:215:
+		ret = dlb2_bitmap_alloc(&hw->vdev[i].avail_hist_list_entries,

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#5333: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:216:
+					DLB2_MAX_NUM_HIST_LIST_ENTRIES);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#5337: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:220:
+		ret = dlb2_bitmap_zero(hw->vdev[i].avail_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#6334: FILE: drivers/event/dlb2/pf/base/dlb2_resource.h:937:
+ * - max_contiguous_hist_list_entries

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#6785: FILE: drivers/event/dlb2/pf/base/dlb2_resource.h:1388:
+ * dlb2_update_vdev_hist_list_entries() - update the vdev's assigned HL entries

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#6807: FILE: drivers/event/dlb2/pf/base/dlb2_resource.h:1410:
+int dlb2_update_vdev_hist_list_entries(struct dlb2_hw *hw, u32 id, u32 num);

WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#8102: FILE: drivers/event/dlb2/pf/dlb2_pf.c:53:
+		dlb2_port[i][DLB2_DIR_PORT].mmaped = true;

WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#8107: FILE: drivers/event/dlb2/pf/dlb2_pf.c:58:
+		dlb2_port[i][DLB2_LDB_PORT].mmaped = true;

total: 0 errors, 70 warnings, 8092 lines checked

          parent reply	other threads:[~2020-10-17 18:24 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1602958879-8558-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=20201017182354.65A5DCA6E@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).