From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pravin Pathak <pravin.pathak@intel.com>
Subject: |WARNING| pw153366 [PATCH v1 4/7] event/dlb2: support managing history list resource
Date: Fri, 9 May 2025 06:26:08 +0200 (CEST) [thread overview]
Message-ID: <20250509042608.0D807123FBC@dpdk.org> (raw)
In-Reply-To: <20250509042401.2634765-5-pravin.pathak@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153366
_coding style issues_
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#175: FILE: drivers/event/dlb2/dlb2.c:984:
+ cfg->num_hist_list_entries = dlb2->hl_entries;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#177: FILE: drivers/event/dlb2/dlb2.c:986:
+ cfg->num_hist_list_entries =
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#224: FILE: drivers/event/dlb2/dlb2.c:1728:
+ if (qm_port->hist_list)
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#225: FILE: drivers/event/dlb2/dlb2.c:1729:
+ cfg.cq_history_list_size = qm_port->hist_list;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#348: FILE: drivers/event/dlb2/dlb2.c:4740:
+ port->hist_list = port_param->port_hl;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#377: FILE: drivers/event/dlb2/dlb2.c:5067:
+ dlb2->hw_rsrc_query_results.num_hist_list_entries) {
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#381: FILE: drivers/event/dlb2/dlb2.c:5071:
+ dlb2->hw_rsrc_query_results.num_hist_list_entries,
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#506: FILE: drivers/event/dlb2/dlb2_priv.h:397:
+ uint16_t hist_list; /* Port history list */
total: 0 errors, 8 warnings, 688 lines checked
Warning in drivers/event/dlb2/dlb2.c:
Using %l format, prefer %PRI*64 if type is [u]int64_t
parent reply other threads:[~2025-05-09 4:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250509042401.2634765-5-pravin.pathak@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=20250509042608.0D807123FBC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pravin.pathak@intel.com \
--cc=test-report@dpdk.org \
/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).