From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Suanming Mou <suanmingm@nvidia.com>
Subject: |WARNING| pw118794 [PATCH v6 08/18] net/mlx5: add HW steering counter action
Date: Thu, 20 Oct 2022 17:44:59 +0200 (CEST) [thread overview]
Message-ID: <20221020154459.B4923120778@dpdk.org> (raw)
In-Reply-To: <20221020154152.28228-9-suanmingm@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/118794
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#1609: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:190:
+ DRV_LOG(ERR, "counter number %"PRIu64" is out of 32bit range",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1609: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:190:
+ DRV_LOG(ERR, "counter number %"PRIu64" is out of 32bit range",
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#1721: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:302:
+ uint32_t idx, alloced = 0;
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#1747: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:328:
+ alloced = cpool->dcs_mng.dcs[0].batch_sz;
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#1758: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:339:
+ cpool->dcs_mng.dcs[idx].iidx = alloced;
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#1759: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:340:
+ alloced += cpool->dcs_mng.dcs[idx].batch_sz;
CHECK:CAMELCASE: Avoid CamelCase: <PRIu32>
#1766: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:347:
+ "Cannot alloc device counter, allocated[%" PRIu32 "] request[%" PRIu32 "]",
WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#1767: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:348:
+ alloced, cnt_num);
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1804: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:385:
+ if (priv->sh->config.dv_esw_en && priv->master)
total: 0 errors, 6 warnings, 3 checks, 2204 lines checked
parent reply other threads:[~2022-10-20 15:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221020154152.28228-9-suanmingm@nvidia.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=20221020154459.B4923120778@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=suanmingm@nvidia.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).