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| pw130389 [PATCH v5 2/2] net/bonding: replace master/slave to main/member
Date: Wed, 16 Aug 2023 08:29:10 +0200 (CEST)	[thread overview]
Message-ID: <20230816062910.C81301206AB@dpdk.org> (raw)
In-Reply-To: <20230816062710.2188087-3-chaoyong.he@corigine.com>

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

_coding style issues_


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

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

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

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

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

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

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

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

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

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#146: 
The data structure ``struct rte_eth_bond_8023ad_slave_info`` was

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#5948: 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'?
#5996: FILE: app/test/test_link_bonding_mode4.c:289:
+	member->lacp_parnter_state = 0;

WARNING:TYPO_SPELLING: 'parnter' may be misspelled - perhaps 'partner'?
#6150: 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'?
#6225: 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'?
#6854: FILE: app/test/test_link_bonding_mode4.c:1356:
+			TEST_ASSERT(member->lacp_parnter_state & STATE_EXPIRED,

WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#8231: FILE: doc/guides/rel_notes/release_23_11.rst:112:
+* bonding: Replace master/slave to main/member. The data structure

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8231: FILE: doc/guides/rel_notes/release_23_11.rst:112:
+* bonding: Replace master/slave to main/member. The data structure

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8232: FILE: doc/guides/rel_notes/release_23_11.rst:113:
+  ``struct rte_eth_bond_8023ad_slave_info`` was renamed to

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8236: FILE: doc/guides/rel_notes/release_23_11.rst:117:
+  ``rte_eth_bond_8023ad_slave_info``,

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#8237: FILE: doc/guides/rel_notes/release_23_11.rst:118:
+  ``rte_eth_bond_active_slaves_get``,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8238: FILE: doc/guides/rel_notes/release_23_11.rst:119:
+  ``rte_eth_bond_slave_add``,

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#8239: FILE: doc/guides/rel_notes/release_23_11.rst:120:
+  ``rte_eth_bond_slave_remove``, and

WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#8240: FILE: doc/guides/rel_notes/release_23_11.rst:121:
+  ``rte_eth_bond_slaves_get``

total: 0 errors, 23 warnings, 13944 lines checked

  parent reply	other threads:[~2023-08-16  6:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230816062710.2188087-3-chaoyong.he@corigine.com>
2023-08-16  6:16 ` |SUCCESS| pw130388-130389 " qemudev
2023-08-16  6:20 ` qemudev
2023-08-16  6:29 ` checkpatch [this message]
2023-08-16  7:19 ` |SUCCESS| pw130389 " 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=20230816062910.C81301206AB@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).