automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [dpdk-test-report] |WARNING| pw97157 [PATCH v3] ethdev: fix representor port ID search by name
Date: Fri, 20 Aug 2021 14:19:40 +0200 (CEST)	[thread overview]
Message-ID: <20210820121940.7345D1226B3@dpdk.org> (raw)
In-Reply-To: <20210820121817.3510013-1-andrew.rybchenko@oktetlabs.ru>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#185: FILE: drivers/net/mlx5/linux/mlx5_os.c:1684:
+			    opriv->master &&

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#194: FILE: drivers/net/mlx5/linux/mlx5_os.c:1693:
+			DRV_LOG(ERR, "no master device for representor");

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#213: FILE: drivers/net/mlx5/windows/mlx5_os.c:550:
+			    opriv->master &&

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#222: FILE: drivers/net/mlx5/windows/mlx5_os.c:559:
+			DRV_LOG(ERR, "no master device for representor");

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#264: FILE: lib/ethdev/rte_class_eth.c:100:
+		 * the master device, but in order to maintain compatibility

total: 0 errors, 5 warnings, 175 lines checked

       reply	other threads:[~2021-08-20 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210820121817.3510013-1-andrew.rybchenko@oktetlabs.ru>
2021-08-20 12:19 ` checkpatch [this message]
2021-08-20 12:59 ` [dpdk-test-report] |SUCCESS| pw97157 [dpdk-dev] " 0-day Robot

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=20210820121940.7345D1226B3@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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).