From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ophir Munk <ophirmu@nvidia.com>
Subject: |WARNING| pw152042 [PATCH V1 2/4] net/mlx5: support FDB unified domain
Date: Tue, 25 Feb 2025 13:05:31 +0100 (CET) [thread overview]
Message-ID: <20250225120531.09F43127817@dpdk.org> (raw)
In-Reply-To: <20250225120213.2968616-2-ophirmu@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152042
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#167: FILE: drivers/net/mlx5/linux/mlx5_os.c:1718:
+ priv->unified_fdb_en = !!priv->master;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#841: FILE: drivers/net/mlx5/mlx5_flow_hw.c:11068:
+ if (priv->sh->config.dv_esw_en && priv->master) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#971: FILE: drivers/net/mlx5/mlx5_flow_hw.c:11690:
+ if (!(priv->sh->config.dv_esw_en && priv->master))
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1192: FILE: drivers/net/mlx5/mlx5_flow_meter.c:195:
+ if (priv->sh->config.dv_esw_en && priv->master) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1213: FILE: drivers/net/mlx5/mlx5_flow_quota.c:744:
+ if (priv->sh->config.dv_esw_en && priv->master) {
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1233: FILE: drivers/net/mlx5/mlx5_hws_cnt.c:669:
+ if (priv->sh->config.dv_esw_en && priv->master) {
total: 0 errors, 6 warnings, 0 checks, 1008 lines checked
parent reply other threads:[~2025-02-25 12:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250225120213.2968616-2-ophirmu@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=20250225120531.09F43127817@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ophirmu@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).