From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: |WARNING| pw133671 [PATCH 6/8] net/mlx5: support port probing of Multiport E-Switch device
Date: Tue, 31 Oct 2023 15:30:56 +0100 (CET) [thread overview]
Message-ID: <20231031143056.79017120A24@dpdk.org> (raw)
In-Reply-To: <20231031142733.2009166-7-dsosnowski@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/133671
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#155:
as a switch master port.
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#470: FILE: drivers/net/mlx5/linux/mlx5_os.c:1249:
+ "dev_port=%u bus=%s pci=%s master=%d representor=%d pf_bond=%d "
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#475: FILE: drivers/net/mlx5/linux/mlx5_os.c:1253:
+ priv->master, priv->representor, priv->pf_bond,
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#530: FILE: drivers/net/mlx5/linux/mlx5_os.c:2132:
+ /* Iterate through IB ports to find MPESW master uplink port. */
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#677: FILE: drivers/net/mlx5/linux/mlx5_os.c:2445:
+ /* Owner port is treated as master port. */
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#679: FILE: drivers/net/mlx5/linux/mlx5_os.c:2447:
+ list[ns].info.master = 1;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#682: FILE: drivers/net/mlx5/linux/mlx5_os.c:2450:
+ list[ns].info.master = 0;
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#915: FILE: drivers/net/mlx5/mlx5_flow_hw.c:9191:
+ info->is_wire = mlx5_is_port_on_mpesw_device(priv) ? priv->mpesw_uplink : priv->master;
total: 0 errors, 8 warnings, 0 checks, 691 lines checked
parent reply other threads:[~2023-10-31 14:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231031142733.2009166-7-dsosnowski@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=20231031143056.79017120A24@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=dsosnowski@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).