From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Feifei Wang <wff_light@vip.163.com>
Subject: |WARNING| pw153020 [RFC 04/18] net/hinic3: add support for cmdq mechanism
Date: Fri, 18 Apr 2025 11:13:20 +0200 (CEST) [thread overview]
Message-ID: <20250418091320.A83D1123FA7@dpdk.org> (raw)
In-Reply-To: <20250418090621.9638-5-wff_light@vip.163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153020
_coding style issues_
WARNING:TYPO_SPELLING: 'coverting' may be misspelled - perhaps 'converting'?
#350: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:268:
+ /* Hardware will do endianness coverting. */
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#890: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:808:
+ &cmdqs->saved_wqs[cmdq_type], cmdq_type);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#912: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:830:
+ hinic3_cmdq_free(cmdqs->saved_wqs, HINIC3_MAX_CMDQ_TYPES);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#920: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:838:
+ size_t saved_wqs_size;
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#931: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:849:
+ saved_wqs_size = HINIC3_MAX_CMDQ_TYPES * sizeof(struct hinic3_wq);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#932: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:850:
+ cmdqs->saved_wqs = rte_zmalloc(NULL, saved_wqs_size, 0);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#932: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:850:
+ cmdqs->saved_wqs = rte_zmalloc(NULL, saved_wqs_size, 0);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#933: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:851:
+ if (!cmdqs->saved_wqs) {
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#934: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:852:
+ PMD_DRV_LOG(ERR, "Allocate saved wqs failed");
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#936: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:854:
+ goto alloc_wqs_err;
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#952: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:870:
+ err = hinic3_cmdq_alloc(cmdqs->saved_wqs, hwdev, HINIC3_MAX_CMDQ_TYPES,
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#971: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:889:
+ rte_free(cmdqs->saved_wqs);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#973: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:891:
+alloc_wqs_err:
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#990: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:908:
+ hinic3_cmdq_free(cmdqs->saved_wqs, HINIC3_MAX_CMDQ_TYPES);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#994: FILE: drivers/net/hinic3/base/hinic3_cmdq.c:912:
+ rte_free(cmdqs->saved_wqs);
WARNING:TYPO_SPELLING: 'wqs' may be misspelled - perhaps 'was'?
#1255: FILE: drivers/net/hinic3/base/hinic3_cmdq.h:192:
+ struct hinic3_wq *saved_wqs;
total: 0 errors, 16 warnings, 0 checks, 1205 lines checked
parent reply other threads:[~2025-04-18 9:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250418090621.9638-5-wff_light@vip.163.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=20250418091320.A83D1123FA7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wff_light@vip.163.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).