From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy McDaniel <timothy.mcdaniel@intel.com>
Subject: [dpdk-test-report] |WARNING| pw81203 [PATCH v2 03/22] event/dlb2: add private data structures and constants
Date: Sat, 17 Oct 2020 20:21:33 +0200 (CEST) [thread overview]
Message-ID: <20201017182133.B2B90CFC7@dpdk.org> (raw)
In-Reply-To: <1602958879-8558-4-git-send-email-timothy.mcdaniel@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/81203
_coding style issues_
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#127: FILE: drivers/event/dlb2/dlb2_priv.h:46:
+#define DLB2_MAX_NUM_HIST_LIST_ENTRIES 2048
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#140: FILE: drivers/event/dlb2/dlb2_priv.h:59:
+/* 2048 total hist list entries and 64 total ldb ports, which
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#141: FILE: drivers/event/dlb2/dlb2_priv.h:60:
+ * makes for 2048/64 == 32 hist list entries per port. However, CQ
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#142: FILE: drivers/event/dlb2/dlb2_priv.h:61:
+ * depth must be a power of 2 and must also be >= HIST LIST entries.
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#148: FILE: drivers/event/dlb2/dlb2_priv.h:67:
+#define DLB2_NUM_HIST_LIST_ENTRIES_PER_LDB_PORT \
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#403: FILE: drivers/event/dlb2/dlb2_priv.h:322:
+ bool mmaped;
total: 0 errors, 6 warnings, 575 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-4-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=20201017182133.B2B90CFC7@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).