From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yunjian Wang <wangyunjian@huawei.com>
Subject: |WARNING| pw113936 [PATCH] net/bonding: fix double get slave link status
Date: Wed, 13 Jul 2022 13:11:46 +0200 (CEST) [thread overview]
Message-ID: <20220713111146.2480F121EFB@dpdk.org> (raw)
In-Reply-To: <598d08fa7e4da0ba42ba21ed3461ead4f6f9d23f.1657710002.git.wangyunjian@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/113936
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#34:
Subject: [dpdk-dev] [PATCH] net/bonding: fix double get slave link status
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#57:
When link status polling mode is using, the slave link status is
WARNING:TYPO_SPELLING: 'lastest' may be misspelled - perhaps 'latest'?
#59:
the lastest queried link state.
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#88: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:2891:
+ uint16_t active_pos, slave_idx;
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#96: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:2912:
+ slave_idx = i;
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#104: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3001:
+ internals->slaves[slave_idx].last_link_status = link.link_status;
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#104: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:3001:
+ internals->slaves[slave_idx].last_link_status = link.link_status;
total: 0 errors, 7 warnings, 0 checks, 31 lines checked
next parent reply other threads:[~2022-07-13 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <598d08fa7e4da0ba42ba21ed3461ead4f6f9d23f.1657710002.git.wangyunjian@huawei.com>
2022-07-13 11:11 ` checkpatch [this message]
2022-07-13 12:18 ` |SUCCESS| pw113936 [dpdk-dev] " 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=20220713111146.2480F121EFB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wangyunjian@huawei.com \
/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).