From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: |WARNING| pw106587 [PATCH] net/bonding: fix MTU set for slaves
Date: Wed, 26 Jan 2022 14:11:17 +0100 (CET) [thread overview]
Message-ID: <20220126131117.B31CC120715@dpdk.org> (raw)
In-Reply-To: <20220126131037.2403369-1-ferruh.yigit@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106587
_coding style issues_
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#48:
Subject: [PATCH] net/bonding: fix MTU set for slaves
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#68:
In bonding PMD, while configuring slaves, bonding first sets MTU later
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#69:
configures them, which causes failure if slaves are not configured in
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#72:
Fixing by changing the order in slave configure as requested in ethdev
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#110: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1754:
+ errval = rte_eth_dev_set_mtu(slave_eth_dev->data->port_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#114: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1758:
+ slave_eth_dev->data->port_id, errval);
total: 0 errors, 6 warnings, 0 checks, 28 lines checked
next parent reply other threads:[~2022-01-26 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220126131037.2403369-1-ferruh.yigit@intel.com>
2022-01-26 13:11 ` checkpatch [this message]
2022-01-26 14:39 ` |SUCCESS| " 0-day Robot
2022-01-28 1:05 |WARNING| " dpdklab
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=20220126131117.B31CC120715@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ferruh.yigit@intel.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).