From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw117932 [PATCH v5] net/bonding: call Tx prepare before Tx burst
Date: Tue, 11 Oct 2022 15:28:01 +0200 (CEST) [thread overview]
Message-ID: <20221011132801.2C590122B85@dpdk.org> (raw)
In-Reply-To: <20221011132033.8547-1-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/117932
_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'?
#106: 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'?
#109: 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'?
#120: 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'?
#123: 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'?
#137: 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'?
#137: 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'?
#138: 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'?
#139: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:607:
+ slave_nb_pkts[i]);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#142: 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'?
#142: 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'?
#181: 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'?
#183: 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'?
#196: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1079:
+ slave_bufs[i], num_send);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#217: 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'?
#217: 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'?
#220: 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:1177:
+ slave_tx_count = rte_eth_tx_burst(slave_port_ids[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#221: 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'?
#222: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1179:
+ slave_tx_count);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#231: 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'?
#231: 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'?
#233: 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:1264:
+ slave_tx_count = rte_eth_tx_burst(slave_port_ids[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#234: 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'?
#243: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1338:
+ nb_pkts = rte_eth_tx_prepare(slaves[0], bd_tx_q->queue_id, bufs, nb_pkts);
total: 0 errors, 27 warnings, 141 lines checked
next parent reply other threads:[~2022-10-11 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221011132033.8547-1-fengchengwen@huawei.com>
2022-10-11 13:28 ` checkpatch [this message]
2022-10-11 14: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=20221011132801.2C590122B85@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).