automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>
Subject: |WARNING| pw126975 [PATCH v2] net/bonding: replace master/slave to main/member
Date: Thu, 18 May 2023 08:34:35 +0200 (CEST)	[thread overview]
Message-ID: <20230518063435.65D2C120927@dpdk.org> (raw)
In-Reply-To: <20230518063202.1529123-1-chaoyong.he@corigine.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#50: 
Subject: [PATCH v2] net/bonding: replace master/slave to main/member

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#50: 
Subject: [PATCH v2] net/bonding: replace master/slave to main/member

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#126: 
This patch replaces the usage of the word 'master/slave' with more

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#126: 
This patch replaces the usage of the word 'master/slave' with more

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#133: 
rte_eth_bond_8023ad_slave_info is now called

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#135: 
rte_eth_bond_active_slaves_get is now called

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#137: 
rte_eth_bond_slave_add is now called

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#139: 
rte_eth_bond_slave_remove is now called

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#141: 
rte_eth_bond_slaves_get is now called

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#144: 
Also the macro RTE_ETH_DEV_BONDED_SLAVE was renamed to

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#5946: FILE: app/test/test_link_bonding_mode4.c:259:
+	RTE_VERIFY(member->lacp_parnter_state == 0);

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#5994: FILE: app/test/test_link_bonding_mode4.c:289:
+	member->lacp_parnter_state = 0;

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#6148: FILE: app/test/test_link_bonding_mode4.c:508:
+	member->lacp_parnter_state = lacp->actor.state;

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#6223: FILE: app/test/test_link_bonding_mode4.c:581:
+	return member->lacp_parnter_state == expected_state;

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#6852: FILE: app/test/test_link_bonding_mode4.c:1356:
+			TEST_ASSERT(member->lacp_parnter_state & STATE_EXPIRED,

CHECK:CAMELCASE: Avoid CamelCase: <BOND_MODE_8023AX_Member_RX_PKTS>
#8479: FILE: drivers/net/bonding/eth_bond_8023ad_private.h:19:
+#define BOND_MODE_8023AX_Member_RX_PKTS        3

CHECK:CAMELCASE: Avoid CamelCase: <BOND_MODE_8023AX_Member_TX_PKTS>
#8481: FILE: drivers/net/bonding/eth_bond_8023ad_private.h:21:
+#define BOND_MODE_8023AX_Member_TX_PKTS        1

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8953: FILE: drivers/net/bonding/rte_eth_bond.h:134:
+rte_eth_bond_slave_add(uint16_t bonded_port_id, uint16_t member_port_id)

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8976: FILE: drivers/net/bonding/rte_eth_bond.h:154:
+rte_eth_bond_slave_remove(uint16_t bonded_port_id, uint16_t member_port_id)

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#9038: FILE: drivers/net/bonding/rte_eth_bond.h:223:
+rte_eth_bond_slaves_get(uint16_t bonded_port_id, uint16_t members[],

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#9069: FILE: drivers/net/bonding/rte_eth_bond.h:248:
+rte_eth_bond_active_slaves_get(uint16_t bonded_port_id, uint16_t members[],

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#10101: FILE: drivers/net/bonding/rte_eth_bond_8023ad.h:203:
+rte_eth_bond_8023ad_slave_info(uint16_t port_id, uint16_t member_id,

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#14758: FILE: lib/ethdev/rte_ethdev.h:2040:
+#define RTE_ETH_DEV_BONDED_SLAVE                         \

WARNING:TYPO_SPELLING: 'SLAVE' may be misspelled - perhaps 'SECONDARY'?
#14760: FILE: lib/ethdev/rte_ethdev.h:2042:
+		RTE_DEPRECATED(RTE_ETH_DEV_BONDED_SLAVE) \

total: 0 errors, 22 warnings, 13937 lines checked

      parent reply	other threads:[~2023-05-18  6:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230518063202.1529123-1-chaoyong.he@corigine.com>
2023-05-18  6:21 ` |SUCCESS| " qemudev
2023-05-18  6:25 ` qemudev
2023-05-18  6:34 ` checkpatch [this message]

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=20230518063435.65D2C120927@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=chaoyong.he@corigine.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).