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| pw77492 [PATCH v4 08/22] event/dlb: add infos get and configure
Date: Fri, 11 Sep 2020 21:25:34 +0200 (CEST)	[thread overview]
Message-ID: <20200911192534.DA2F01C139@dpdk.org> (raw)
In-Reply-To: <1599851920-16802-9-git-send-email-timothy.mcdaniel@intel.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#267: FILE: drivers/event/dlb/dlb.c:415:
+	config_params->num_hist_list_entries = config_params->num_ldb_ports *

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#268: FILE: drivers/event/dlb/dlb.c:416:
+		DLB_NUM_HIST_LIST_ENTRIES_PER_LDB_PORT;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#274: FILE: drivers/event/dlb/dlb.c:422:
+	DLB_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, ldb_cred_pools=%d, dir-credit_pools=%d
",

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

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

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#675: FILE: drivers/event/dlb/pf/base/dlb_resource.c:33:
+	DLB_CSR_RD(hw, DLB_SYS_TOTAL_VAS);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1150: FILE: drivers/event/dlb/pf/base/dlb_resource.c:681:
+dlb_attach_domain_hist_list_entries(struct dlb_function_resources *rsrcs,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1152: FILE: drivers/event/dlb/pf/base/dlb_resource.c:683:
+				    u32 num_hist_list_entries,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1158: FILE: drivers/event/dlb/pf/base/dlb_resource.c:689:
+	if (num_hist_list_entries) {

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1159: FILE: drivers/event/dlb/pf/base/dlb_resource.c:690:
+		bitmap = rsrcs->avail_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1162: FILE: drivers/event/dlb/pf/base/dlb_resource.c:693:
+						     num_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1166: FILE: drivers/event/dlb/pf/base/dlb_resource.c:697:
+		domain->total_hist_list_entries = num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1166: FILE: drivers/event/dlb/pf/base/dlb_resource.c:697:
+		domain->total_hist_list_entries = num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1167: FILE: drivers/event/dlb/pf/base/dlb_resource.c:698:
+		domain->avail_hist_list_entries = num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1167: FILE: drivers/event/dlb/pf/base/dlb_resource.c:698:
+		domain->avail_hist_list_entries = num_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1168: FILE: drivers/event/dlb/pf/base/dlb_resource.c:699:
+		domain->hist_list_entry_base = base;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1169: FILE: drivers/event/dlb/pf/base/dlb_resource.c:700:
+		domain->hist_list_entry_offset = 0;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1171: FILE: drivers/event/dlb/pf/base/dlb_resource.c:702:
+		dlb_bitmap_clear_range(bitmap, base, num_hist_list_entries);

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#1176: FILE: drivers/event/dlb/pf/base/dlb_resource.c:707:
+	resp->status = DLB_ST_HIST_LIST_ENTRIES_UNAVAILABLE;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1273: FILE: drivers/event/dlb/pf/base/dlb_resource.c:804:
+	ret = dlb_attach_domain_hist_list_entries(rsrcs,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1275: FILE: drivers/event/dlb/pf/base/dlb_resource.c:806:
+						  args->num_hist_list_entries,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#2143: FILE: drivers/event/dlb/pf/base/dlb_resource.c:1674:
+		dlb_bitmap_longest_set_range(rsrcs->avail_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#2169: FILE: drivers/event/dlb/pf/base/dlb_resource.c:1700:
+	else if (max_contig_hl_entries < args->num_hist_list_entries)

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#2170: FILE: drivers/event/dlb/pf/base/dlb_resource.c:1701:
+		resp->status = DLB_ST_HIST_LIST_ENTRIES_UNAVAILABLE;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#2215: FILE: drivers/event/dlb/pf/base/dlb_resource.c:1746:
+	DLB_HW_INFO(hw, "	Number of hist list entries: %d
",

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#2216: FILE: drivers/event/dlb/pf/base/dlb_resource.c:1747:
+		    args->num_hist_list_entries);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2774: FILE: drivers/event/dlb/pf/base/dlb_resource.c:2305:
+	r0.field.en_tim = 0;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#2817: FILE: drivers/event/dlb/pf/base/dlb_resource.c:2348:
+	r0.field.en_tim = 0;

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3826: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3357:
+		   DLB_CHP_HIST_LIST_LIM(port->id),

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3827: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3358:
+		   DLB_CHP_HIST_LIST_LIM_RST);

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3830: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3361:
+		   DLB_CHP_HIST_LIST_BASE(port->id),

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3831: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3362:
+		   DLB_CHP_HIST_LIST_BASE_RST);

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3834: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3365:
+		   DLB_CHP_HIST_LIST_POP_PTR(port->id),

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3835: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3366:
+		   DLB_CHP_HIST_LIST_POP_PTR_RST);

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3838: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3369:
+		   DLB_CHP_HIST_LIST_PUSH_PTR(port->id),

WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#3839: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3370:
+		   DLB_CHP_HIST_LIST_PUSH_PTR_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3910: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3441:
+		   DLB_SYS_LDB_PP2VAS(port->id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#3911: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3442:
+		   DLB_SYS_LDB_PP2VAS_RST);

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#4055: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3586:
+		   DLB_SYS_DIR_PP2VAS(port->id),

WARNING:TYPO_SPELLING: 'VAS' may be misspelled - perhaps 'WAS'?
#4056: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3587:
+		   DLB_SYS_DIR_PP2VAS_RST);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4355: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3886:
+	/* Return hist list entries to the function */

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4356: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3887:
+	ret = dlb_bitmap_set_range(rsrcs->avail_hist_list_entries,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4357: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3888:
+				   domain->hist_list_entry_base,

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4358: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3889:
+				   domain->total_hist_list_entries);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4361: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3892:
+			   "[%s()] Internal error: domain hist list base does not match the function's bitmap.
",

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4366: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3897:
+	domain->total_hist_list_entries = 0;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4367: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3898:
+	domain->avail_hist_list_entries = 0;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4368: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3899:
+	domain->hist_list_entry_base = 0;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4369: FILE: drivers/event/dlb/pf/base/dlb_resource.c:3900:
+	domain->hist_list_entry_offset = 0;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4650: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4181:
+	map = rsrcs->avail_hist_list_entries;

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4652: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4183:
+	arg->num_hist_list_entries = dlb_bitmap_count(map);

WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#4654: FILE: drivers/event/dlb/pf/base/dlb_resource.c:4185:
+	arg->max_contiguous_hist_list_entries =

total: 0 errors, 52 warnings, 4691 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-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=20200911192534.DA2F01C139@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).