[dpdk-test-report] |WARNING| pw81968 [PATCH v3 06/23] event/dlb2: add eventdev 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| pw81968 [PATCH v3 06/23] event/dlb2: add eventdev probe
Date: Fri, 23 Oct 2020 20:31:59 +0200 (CEST)	[thread overview]
Message-ID: <20201023183159.6EBC15A6C@dpdk.org> (raw)
In-Reply-To: <1603477826-31374-7-git-send-email-timothy.mcdaniel@intel.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#502: 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'?
#689: 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'?
#690: 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'?
#759: 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'?
#760: 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'?
#761: 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'?
#762: 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'?
#782: 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'?
#1059: FILE: drivers/event/dlb2/pf/base/dlb2_mbox.h:205:
+	u32 num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1060: 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'?
#1072: FILE: drivers/event/dlb2/pf/base/dlb2_mbox.h:218:
+	u32 num_hist_list_entries;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2481: 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'?
#2482: 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'?
#2483: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:171:
+union dlb2_sys_total_vas {

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

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2923: 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'?
#2925: 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'?
#2926: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:614:
+union dlb2_sys_ldb_pp2vas {

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

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3061: 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'?
#3063: 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'?
#3064: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:752:
+union dlb2_sys_dir_pp2vas {

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

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3410: 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'?
#3412: 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'?
#3413: 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'?
#3421: 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'?
#3423: 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'?
#3424: 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'?
#3496: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1184:
+		u32 en_tim : 1;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3548: 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'?
#3550: 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'?
#3551: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1239:
+union dlb2_chp_dir_cq2vas {

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

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3559: 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'?
#3561: 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'?
#3562: 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'?
#3570: 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'?
#3572: 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'?
#3573: 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'?
#3581: 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'?
#3583: 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'?
#3584: 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'?
#3593: 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'?
#3595: 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'?
#3596: 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'?
#3632: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1320:
+		u32 en_tim : 1;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3684: 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'?
#3686: 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'?
#3687: FILE: drivers/event/dlb2/pf/base/dlb2_regs.h:1375:
+union dlb2_chp_ldb_cq2vas {

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

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

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#6233: 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'?
#6255: 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);

total: 0 errors, 54 warnings, 7509 lines checked

          parent reply	other threads:[~2020-10-23 18:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1603477826-31374-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=20201023183159.6EBC15A6C@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).