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| pw77518 [PATCH 11/22] event/dlb2: add port setup
Date: Fri, 11 Sep 2020 22:33:36 +0200 (CEST)	[thread overview]
Message-ID: <20200911203336.776111C1F2@dpdk.org> (raw)
In-Reply-To: <1599855987-25976-12-git-send-email-timothy.mcdaniel@intel.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#227: FILE: drivers/event/dlb2/dlb2.c:1191:
+	cfg.cq_history_list_size = DLB2_NUM_HIST_LIST_ENTRIES_PER_LDB_PORT;

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#668: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3980:
+	union dlb2_sys_ldb_pp2vas r0 = { {0} };

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#671: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3983:
+	r0.field.vas = domain->id.phys_id;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#673: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3985:
+	DLB2_CSR_WR(hw, DLB2_SYS_LDB_PP2VAS(port->id.phys_id), r0.val);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#731: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4043:
+	union dlb2_chp_hist_list_lim r5 = { {0} };

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#732: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4044:
+	union dlb2_chp_hist_list_base r6 = { {0} };

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#734: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4046:
+	union dlb2_chp_hist_list_push_ptr r8 = { {0} };

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#735: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4047:
+	union dlb2_chp_hist_list_pop_ptr r9 = { {0} };

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#738: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4050:
+	union dlb2_chp_ldb_cq2vas r12 = { {0} };

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#824: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4136:
+	r5.field.limit = port->hist_list_entry_limit - 1;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#826: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4138:
+	DLB2_CSR_WR(hw, DLB2_CHP_HIST_LIST_LIM(port->id.phys_id), r5.val);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#828: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4140:
+	r6.field.base = port->hist_list_entry_base;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#830: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4142:
+	DLB2_CSR_WR(hw, DLB2_CHP_HIST_LIST_BASE(port->id.phys_id), r6.val);

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#844: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4156:
+		    DLB2_CHP_HIST_LIST_PUSH_PTR(port->id.phys_id),

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#850: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4162:
+	DLB2_CSR_WR(hw, DLB2_CHP_HIST_LIST_POP_PTR(port->id.phys_id), r9.val);

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#869: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4181:
+	r12.field.cq2vas = domain->id.phys_id;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#871: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4183:
+	DLB2_CSR_WR(hw, DLB2_CHP_LDB_CQ2VAS(port->id.phys_id), r12.val);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#891: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4203:
+	port->hist_list_entry_base = domain->hist_list_entry_base +

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#891: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4203:
+	port->hist_list_entry_base = domain->hist_list_entry_base +

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#892: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4204:
+				     domain->hist_list_entry_offset;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#893: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4205:
+	port->hist_list_entry_limit = port->hist_list_entry_base +

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#893: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4205:
+	port->hist_list_entry_limit = port->hist_list_entry_base +

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#896: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4208:
+	domain->hist_list_entry_offset += args->cq_history_list_size;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#897: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4209:
+	domain->avail_hist_list_entries -= args->cq_history_list_size;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#943: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4255:
+	DLB2_HW_DBG(hw, "	CQ hist list size:         %d
",

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1026: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4338:
+		resp->status = DLB2_ST_INVALID_HIST_LIST_DEPTH;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1030: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4342:
+	if (args->cq_history_list_size > domain->avail_hist_list_entries) {

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1031: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4343:
+		resp->status = DLB2_ST_HIST_LIST_ENTRIES_UNAVAILABLE;

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1277: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4589:
+	union dlb2_sys_dir_pp2vas r0 = { {0} };

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1280: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4592:
+	r0.field.vas = domain->id.phys_id;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#1282: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4594:
+	DLB2_CSR_WR(hw, DLB2_SYS_DIR_PP2VAS(port->id.phys_id), r0.val);

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1343: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4655:
+	union dlb2_chp_dir_cq2vas r12 = { {0} };

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#1451: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4763:
+	r12.field.cq2vas = domain->id.phys_id;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#1453: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:4765:
+	DLB2_CSR_WR(hw, DLB2_CHP_DIR_CQ2VAS(port->id.phys_id), r12.val);

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1637: FILE: drivers/event/dlb2/pf/dlb2_pf.c:248:
+		core_id = rte_get_master_lcore();

total: 0 errors, 35 warnings, 1709 lines checked

           reply	other threads:[~2020-09-11 20:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1599855987-25976-12-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=20200911203336.776111C1F2@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).