From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengchang Tang <tangchengchang@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw92067 [PATCH 1/2] net/bonding: support Tx prepare for bonding
Date: Fri, 23 Apr 2021 11:47:50 +0200 (CEST) [thread overview]
Message-ID: <20210423094750.3BCEB121159@dpdk.org> (raw)
In-Reply-To: <1619171202-28486-2-git-send-email-tangchengchang@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92067
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#64:
allocates the packets to different slave devices based on the real-time
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#66:
bonding device to determine which slave device's prepare function should
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#75:
If tx_prepare is not required in some cases, then slave PMDs tx_prepare
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#78:
the responsibility of the slave PMDs to decide when the real tx_prepare
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#84:
because in broadcast mode, a packet needs to be sent by all slave ports.
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#119: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:611:
+ nb_prep_pkts = rte_eth_tx_prepare(slaves[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#120: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:612:
+ bd_tx_q->queue_id, slave_bufs[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#121: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:613:
+ slave_nb_pkts[i]);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#125: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:616:
+ slave_bufs[i], nb_prep_pkts);
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#164: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:970:
+ nb_prep_pkts = rte_eth_tx_prepare(slaves[i], bd_tx_q->queue_id,
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#167: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:973:
+ num_tx_total += rte_eth_tx_burst(slaves[i], bd_tx_q->queue_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#181: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1181:
+ nb_prep_pkts = rte_eth_tx_prepare(slave_port_ids[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#182: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1182:
+ bd_tx_q->queue_id, slave_bufs[i],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#183: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1183:
+ slave_nb_bufs[i]);
total: 0 errors, 14 warnings, 0 checks, 80 lines checked
parent reply other threads:[~2021-04-23 9:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1619171202-28486-2-git-send-email-tangchengchang@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=20210423094750.3BCEB121159@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=tangchengchang@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).