automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw117713 [PATCH v4] net/bonding: call Tx prepare before Tx burst
Date: Sun,  9 Oct 2022 05:42:52 +0200 (CEST)	[thread overview]
Message-ID: <20221009034253.01BB0120EFA@dpdk.org> (raw)
In-Reply-To: <20221009033639.38232-1-fengchengwen@huawei.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#63: 
allocates the packets to different slave devices based on the real-time

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#65: 
bonded device to determine which slave device's prepare function should

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#105: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:639:
+		uint16_t pkts_sent = rte_eth_tx_prepare(slave_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#108: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:642:
+		pkts_sent = rte_eth_tx_burst(slave_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#119: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:1377:
+			uint16_t tx_count = rte_eth_tx_prepare(slave_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#122: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:1380:
+			tx_count = rte_eth_tx_burst(slave_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#136: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:605:
+			num_tx_slave = rte_eth_tx_prepare(slaves[i],

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#136: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:605:
+			num_tx_slave = rte_eth_tx_prepare(slaves[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#137: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:606:
+					bd_tx_q->queue_id, slave_bufs[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#138: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:607:
+					slave_nb_pkts[i]);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#141: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:609:
+					slave_bufs[i], num_tx_slave);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#141: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:609:
+					slave_bufs[i], num_tx_slave);

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#180: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:961:
+		num_tx_prep = rte_eth_tx_prepare(slaves[i], bd_tx_q->queue_id,

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#182: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:963:
+		num_tx_total += rte_eth_tx_burst(slaves[i], bd_tx_q->queue_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#195: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1079:
+					slave_bufs[i], num_send);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#216: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1174:
+		slave_tx_count = rte_eth_tx_prepare(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#216: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1174:
+		slave_tx_count = rte_eth_tx_prepare(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#219: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1177:
+		slave_tx_count = rte_eth_tx_burst(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#219: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1177:
+		slave_tx_count = rte_eth_tx_burst(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#220: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1178:
+				bd_tx_q->queue_id, slave_bufs[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#221: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1179:
+				slave_tx_count);

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#230: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1262:
+			slave_tx_count = rte_eth_tx_prepare(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#230: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1262:
+			slave_tx_count = rte_eth_tx_prepare(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#232: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1264:
+			slave_tx_count = rte_eth_tx_burst(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#232: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1264:
+			slave_tx_count = rte_eth_tx_burst(slave_port_ids[i],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#233: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1265:
+					bd_tx_q->queue_id, &ctrl_pkt, slave_tx_count);

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#250: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1343:
+	num_tx_prep = rte_eth_tx_prepare(slaves[0], bd_tx_q->queue_id,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#262: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1353:
+		if (unlikely(slave_tx_total[i] < num_tx_prep))

total: 0 errors, 28 warnings, 159 lines checked

       reply	other threads:[~2022-10-09  3:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221009033639.38232-1-fengchengwen@huawei.com>
2022-10-09  3:42 ` checkpatch [this message]
2022-10-09  4:59 ` |SUCCESS| " 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=20221009034253.01BB0120EFA@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=fengchengwen@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).