From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw116408 [PATCH v3 1/3] net/bonding: support Tx prepare
Date: Sat, 17 Sep 2022 06:23:25 +0200 (CEST) [thread overview]
Message-ID: <20220917042325.1ECA912210E@dpdk.org> (raw)
In-Reply-To: <20220917041537.6821-2-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/116408
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#66:
allocates the packets to different slave devices based on the real-time
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#68:
bonded device to determine which slave device's prepare function should
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#85:
[1]: In bond mode 3 (broadcast), a packet needs to be sent by all slave
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#86:
ports. Different slave PMDs process the packets differently in
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#87:
tx_prepare. If call tx_prepare before each slave port sending, the sent
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#89:
[2]: https://inbox.dpdk.org/dev/1618571071-5927-2-git-send-email-tangchengchang@huawei.com/
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#156: FILE: drivers/net/bonding/eth_bond_private.h:264:
+ uint16_t slave_port_id, uint16_t queue_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#208: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:640:
+ slave_id, internals->mode4.dedicated_queues.tx_qid,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#219: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:1375:
+ slave_id, internals->mode4.dedicated_queues.tx_qid,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#274: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:565:
+ uint16_t slave_port_id, uint16_t queue_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#280: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:571:
+ nb_pre = rte_eth_tx_prepare(slave_port_id, queue_id, tx_pkts,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#283: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:574:
+ return rte_eth_tx_burst(slave_port_id, queue_id, tx_pkts, nb_pre);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#292: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:583:
+bond_ethdev_tx_user_wrap(struct bond_tx_queue *bd_tx_q, uint16_t slave_port_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#306: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:597:
+ nb_pre = rte_eth_tx_prepare(slave_port_id, queue_id, tx_pkts, nb_pkts);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#314: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:605:
+ nb_pre = rte_eth_tx_prepare(slave_port_id, queue_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#337: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:628:
+ return fail_cnt + rte_eth_tx_burst(slave_port_id, queue_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#350: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:675:
+ num_tx_slave = bond_ethdev_tx_user_wrap(bd_tx_q,
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#351: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:676:
+ slaves[i], slave_bufs[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#351: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:676:
+ slaves[i], slave_bufs[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#352: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:677:
+ slave_nb_pkts[i]);
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#373: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1025:
+ num_tx_total += bond_ethdev_tx_user_wrap(bd_tx_q, slaves[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#385: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1139:
+ bd_tx_q->queue_id, slave_bufs[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#386: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1140:
+ slave_bufs_pkts[i]);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#407: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1234:
+ slave_tx_count = bond_ethdev_tx_user_wrap(bd_tx_q,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#408: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1235:
+ slave_port_ids[i], slave_bufs[i], slave_nb_bufs[i]);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#408: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1235:
+ slave_port_ids[i], slave_bufs[i], slave_nb_bufs[i]);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#408: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1235:
+ slave_port_ids[i], slave_bufs[i], slave_nb_bufs[i]);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#418: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1318:
+ slave_tx_count = bond_ethdev_tx_ctrl_wrap(internals,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#419: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1319:
+ slave_port_ids[i], bd_tx_q->queue_id,
total: 0 errors, 29 warnings, 0 checks, 283 lines checked
parent reply other threads:[~2022-09-17 4:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220917041537.6821-2-fengchengwen@huawei.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=20220917042325.1ECA912210E@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).