automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Min Hu (Connor)" <humin29@huawei.com>
Subject: |WARNING| pw108526 [PATCH] net/bonding: fix slaves initializing on mtu setting
Date: Fri,  4 Mar 2022 02:24:33 +0100 (CET)	[thread overview]
Message-ID: <20220304012433.AD37E1234A0@dpdk.org> (raw)
In-Reply-To: <20220304012257.39247-5-humin29@huawei.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#33: 
Subject: [PATCH] net/bonding: fix slaves initializing on mtu setting

WARNING:TYPO_SPELLING: 'Wan' may be misspelled - perhaps 'Want'?
#58: 
From: Wan Junjie <wanjunjie@bytedance.com>

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#66: 
-a 0000:af:00.0 --vdev="net_bonding0,mode=2,slave=0000:af:00.0"

WARNING:TYPO_SPELLING: 'compain' may be misspelled - perhaps 'complain'?
#68: 
It will fail and compain for the slave device

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#68: 
It will fail and compain for the slave device

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#123: FILE: drivers/net/bonding/eth_bond_private.h:250:
+slave_start(struct rte_eth_dev *bonded_eth_dev,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#124: FILE: drivers/net/bonding/eth_bond_private.h:251:
+		struct rte_eth_dev *slave_eth_dev);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#137: FILE: drivers/net/bonding/rte_eth_bond_api.c:569:
+		if (slave_start(bonded_eth_dev, slave_eth_dev) != 0) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#137: FILE: drivers/net/bonding/rte_eth_bond_api.c:569:
+		if (slave_start(bonded_eth_dev, slave_eth_dev) != 0) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#138: FILE: drivers/net/bonding/rte_eth_bond_api.c:570:
+			internals->slave_count--;

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#139: FILE: drivers/net/bonding/rte_eth_bond_api.c:571:
+			RTE_BOND_LOG(ERR, "rte_bond_slaves_start: port=%d",

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#140: FILE: drivers/net/bonding/rte_eth_bond_api.c:572:
+					slave_port_id);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#173: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1761:
+slave_start(struct rte_eth_dev *bonded_eth_dev,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#174: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1762:
+		struct rte_eth_dev *slave_eth_dev)

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#191: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1818:
+		if (internals->mode4.dedicated_queues.flow[slave_eth_dev->data->port_id] != NULL) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#192: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1819:
+			errval = rte_flow_destroy(slave_eth_dev->data->port_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#196: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1823:
+				slave_eth_dev->data->port_id, errval);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#205: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:2016:
+		if (slave_start(eth_dev, slave_ethdev) != 0) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#205: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:2016:
+		if (slave_start(eth_dev, slave_ethdev) != 0) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#207: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:2018:
+				"bonded port (%d) failed to start slave device (%d)",

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#209: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:2020:
+				internals->slaves[i].port_id);

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#219: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3869:
+	/* configure slaves so we can pass mtu setting */

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#220: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3870:
+	for (i = 0; i < internals->slave_count; i++) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#221: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3871:
+		struct rte_eth_dev *slave_ethdev =

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#222: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3872:
+				&(rte_eth_devices[internals->slaves[i].port_id]);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#223: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3873:
+		if (slave_configure(dev, slave_ethdev) != 0) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#223: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3873:
+		if (slave_configure(dev, slave_ethdev) != 0) {

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#225: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3875:
+				"bonded port (%d) failed to configure slave device (%d)",

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#227: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3877:
+				internals->slaves[i].port_id);

total: 0 errors, 29 warnings, 0 checks, 121 lines checked

       reply	other threads:[~2022-03-04  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220304012257.39247-5-humin29@huawei.com>
2022-03-04  1:24 ` checkpatch [this message]
2022-03-04  3:19 ` |SUCCESS| " 0-day Robot
2022-03-04  1:38 |WARNING| " dpdklab

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=20220304012433.AD37E1234A0@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=humin29@huawei.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).