[dpdk-test-report] |WARNING| pw77513 [PATCH 08/22] event/dlb2: add infos get and configure

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| pw77513 [PATCH 08/22] event/dlb2: add infos get and configure
Date: Fri, 11 Sep 2020 22:32:29 +0200 (CEST)	[thread overview]
Message-ID: <20200911203229.8E2A81C1C2@dpdk.org> (raw)
In-Reply-To: <1599855987-25976-9-git-send-email-timothy.mcdaniel@intel.com>

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

_coding style issues_


WARNING:PREFER_FALLTHROUGH: Prefer 'fallthrough;' over fallthrough comment
#121: FILE: drivers/event/dlb2/dlb2.c:403:
+		/* fn is void, so fall through and return values set up in

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#218: FILE: drivers/event/dlb2/dlb2.c:500:
+	config_params->num_hist_list_entries = resources_asked->num_ldb_ports *

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#219: FILE: drivers/event/dlb2/dlb2.c:501:
+		DLB2_NUM_HIST_LIST_ENTRIES_PER_LDB_PORT;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#221: FILE: drivers/event/dlb2/dlb2.c:503:
+	DLB2_LOG_DBG("sched domain create - ldb_qs=%d, ldb_ports=%d, dir_ports=%d, atomic_inflights=%d, hist_list_entries=%d, ldb_credits=%d, dir_credits=%d
",

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#226: FILE: drivers/event/dlb2/dlb2.c:508:
+		     config_params->num_hist_list_entries,

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

WARNING:TYPO_SPELLING: 'vas' may be misspelled - perhaps 'was'?
#495: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:298:
+	union dlb2_chp_cfg_dir_vas_crd r1 = { {0} };

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

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#503: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:306:
+	DLB2_CSR_WR(hw, DLB2_CHP_CFG_DIR_VAS_CRD(domain->id.phys_id), r1.val);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#796: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:599:
+dlb2_attach_domain_hist_list_entries(struct dlb2_function_resources *rsrcs,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#798: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:601:
+				     u32 num_hist_list_entries,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#804: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:607:
+	if (num_hist_list_entries) {

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

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#808: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:611:
+						      num_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#812: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:615:
+		domain->total_hist_list_entries = num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#812: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:615:
+		domain->total_hist_list_entries = num_hist_list_entries;

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

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

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

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

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#817: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:620:
+		dlb2_bitmap_clear_range(bitmap, base, num_hist_list_entries);

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

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#911: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:714:
+	ret = dlb2_attach_domain_hist_list_entries(rsrcs,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#913: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:716:
+						   args->num_hist_list_entries,

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

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1008: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:811:
+	if (max_contig_hl_range < args->num_hist_list_entries) {

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

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1043: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:846:
+	DLB2_HW_DBG(hw, "	Number of hist list entries:   %d
",

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1044: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:847:
+		    args->num_hist_list_entries);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#1129: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:932:
+	DLB2_CSR_RD(hw, DLB2_SYS_TOTAL_VAS);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2616: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2419:
+	r0.field.en_tim = 0;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2644: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2447:
+	r0.field.en_tim = 0;

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2891: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2694:
+		    DLB2_SYS_LDB_PP2VAS(port->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2892: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2695:
+		    DLB2_SYS_LDB_PP2VAS_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2895: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2698:
+		    DLB2_CHP_LDB_CQ2VAS(port->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#2896: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2699:
+		    DLB2_CHP_LDB_CQ2VAS_RST);

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

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

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

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

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

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

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

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

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3053: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2856:
+		    DLB2_CHP_DIR_CQ2VAS(port->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3054: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2857:
+		    DLB2_CHP_DIR_CQ2VAS_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3131: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2934:
+		    DLB2_SYS_DIR_PP2VAS(port->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3132: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2935:
+		    DLB2_SYS_DIR_PP2VAS_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3135: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2938:
+		    DLB2_CHP_DIR_CQ2VAS(port->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3136: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:2939:
+		    DLB2_CHP_DIR_CQ2VAS_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3325: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3128:
+		    DLB2_CHP_CFG_LDB_VAS_CRD(domain->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3326: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3129:
+		    DLB2_CHP_CFG_LDB_VAS_CRD_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3329: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3132:
+		    DLB2_CHP_CFG_DIR_VAS_CRD(domain->id.phys_id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3330: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3133:
+		    DLB2_CHP_CFG_DIR_VAS_CRD_RST);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3452: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3255:
+	/* Return hist list entries to the function */

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3453: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3256:
+	ret = dlb2_bitmap_set_range(rsrcs->avail_hist_list_entries,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3454: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3257:
+				    domain->hist_list_entry_base,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3455: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3258:
+				    domain->total_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3458: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3261:
+			    "[%s()] Internal error: domain hist list base doesn't match the function's bitmap.
",

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#3463: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:3266:
+	domain->total_hist_list_entries = 0;

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

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

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

total: 0 errors, 63 warnings, 3689 lines checked

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

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