From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw81202 [PATCH v2 04/22] event/dlb2: add definitions shared with LKM or shared code
Date: Sat, 17 Oct 2020 20:21:28 +0200 (CEST) [thread overview]
Message-ID: <20201017182128.9611CCF69@dpdk.org> (raw)
In-Reply-To: <1602958879-8558-5-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/81202
_coding style issues_
WARNING:TYPO_SPELLING: 'definit' may be misspelled - perhaps 'definite'?
#47:
Subject: [dpdk-dev] =?utf-8?q?=5BPATCH_v2_04/22=5D_event/dlb2=3A_add_definit?=
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#109: FILE: drivers/event/dlb2/dlb2_user.h:25:
+ DLB2_ST_HIST_LIST_ENTRIES_UNAVAILABLE,
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#129: FILE: drivers/event/dlb2/dlb2_user.h:45:
+ DLB2_ST_INVALID_HIST_LIST_DEPTH,
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#148: FILE: drivers/event/dlb2/dlb2_user.h:64:
+ "DLB2_ST_HIST_LIST_ENTRIES_UNAVAILABLE",
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#168: FILE: drivers/event/dlb2/dlb2_user.h:84:
+ "DLB2_ST_INVALID_HIST_LIST_DEPTH",
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#224: FILE: drivers/event/dlb2/dlb2_user.h:140:
+ * - num_hist_list_entries: Amount of history list storage. This is divided
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#256: FILE: drivers/event/dlb2/dlb2_user.h:172:
+ __u32 num_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#276: FILE: drivers/event/dlb2/dlb2_user.h:192:
+ * - num_hist_list_entries: Amount of history list storage.
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#277: FILE: drivers/event/dlb2/dlb2_user.h:193:
+ * - max_contiguous_hist_list_entries: History list storage is allocated in
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#291: FILE: drivers/event/dlb2/dlb2_user.h:207:
+ __u32 num_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#292: FILE: drivers/event/dlb2/dlb2_user.h:208:
+ __u32 max_contiguous_hist_list_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#511: FILE: drivers/event/dlb2/dlb2_user.h:427:
+ * - num_hist_list_entries: Number of history list entries. This must be
total: 0 errors, 12 warnings, 679 lines checked
parent reply other threads:[~2020-10-17 18:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1602958879-8558-5-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=20201017182128.9611CCF69@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).