automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <michaelba@nvidia.com>
Subject: [dpdk-test-report] |WARNING| pw102314 [PATCH v3 08/18] common/mlx5: share device context object
Date: Tue, 19 Oct 2021 22:59:13 +0200 (CEST)	[thread overview]
Message-ID: <20211019205913.E5B6E120E1D@dpdk.org> (raw)
In-Reply-To: <20211019205602.3188203-9-michaelba@nvidia.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/102314

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#952: FILE: drivers/net/mlx5/linux/mlx5_os.c:1948:
+	 * Try to get master device name. If something goes wrong suppose

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#970: FILE: drivers/net/mlx5/linux/mlx5_os.c:1960:
+	 * The master device might not be on the predefined port(not on port

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#972: FILE: drivers/net/mlx5/linux/mlx5_os.c:1962:
+	 * device ports and find master.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#1022: FILE: drivers/net/mlx5/linux/mlx5_os.c:2174:
+				"PCI information matches for slave %d bonding device \"%s\"",

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#1066: FILE: drivers/net/mlx5/linux/mlx5_os.c:2432:
+		 * device as master. Override this if there is the single

total: 0 errors, 5 warnings, 1941 lines checked

           reply	other threads:[~2021-10-19 20:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20211019205602.3188203-9-michaelba@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=20211019205913.E5B6E120E1D@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=michaelba@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).