From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw77489 [PATCH v4 07/22] event/dlb: add xstats
Date: Fri, 11 Sep 2020 21:24:39 +0200 (CEST) [thread overview]
Message-ID: <20200911192439.042F31C1BB@dpdk.org> (raw)
In-Reply-To: <1599851920-16802-8-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/77489
_coding style issues_
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#378: FILE: drivers/event/dlb/dlb_xstats.c:254:
+ return DLB_NUM_HIST_LIST_ENTRIES_PER_LDB_PORT;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1138: FILE: drivers/event/dlb/dlb_xstats.c:1014:
+ fprintf(f, "num atomic inflights=%u, hist list entries=%u
",
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1140: FILE: drivers/event/dlb/dlb_xstats.c:1016:
+ handle->cfg.resources.num_hist_list_entries);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1162: FILE: drivers/event/dlb/dlb_xstats.c:1038:
+ fprintf(f, " num_hist_list_entries = %u
",
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1163: FILE: drivers/event/dlb/dlb_xstats.c:1039:
+ dlb->hw_rsrc_query_results.num_hist_list_entries);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1165: FILE: drivers/event/dlb/dlb_xstats.c:1041:
+ fprintf(f, " max_contiguous_hist_list_entries = %u
",
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#1166: FILE: drivers/event/dlb/dlb_xstats.c:1042:
+ dlb->hw_rsrc_query_results.max_contiguous_hist_list_entries);
total: 0 errors, 7 warnings, 1300 lines checked
parent reply other threads:[~2020-09-11 19:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1599851920-16802-8-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=20200911192439.042F31C1BB@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).