From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dongdong Liu <liudongdong3@huawei.com>
Subject: |WARNING| pw112551 [PATCH 1/2] net/bonding: fix RSS inconsistent between bonded and slaves
Date: Wed, 8 Jun 2022 13:46:50 +0200 (CEST) [thread overview]
Message-ID: <20220608114650.DB550121D20@dpdk.org> (raw)
In-Reply-To: <20220608114548.25837-2-liudongdong3@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/112551
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#61:
Currently, RSS configuration of slave is set only when RSS is enabled for
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#62:
bonded port. If RSS is enabled for the slaves port before adding to the
WARNING:TYPO_SPELLING: 'slaves' may be misspelled - perhaps 'secondaries'?
#64:
of bonded and slaves port is inconsistent after starting bonded port.
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#65:
So the RSS configuration of slave should also be set when RSS is disabled
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#86: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1711:
+ slave_eth_dev->data->dev_conf.rx_adv_conf.rss_conf.rss_key_len = 0;
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#87: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1712:
+ slave_eth_dev->data->dev_conf.rx_adv_conf.rss_conf.rss_key = NULL;
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#88: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1713:
+ slave_eth_dev->data->dev_conf.rx_adv_conf.rss_conf.rss_hf = 0;
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#89: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1714:
+ slave_eth_dev->data->dev_conf.rxmode.mq_mode =
total: 0 errors, 8 warnings, 0 checks, 12 lines checked
parent reply other threads:[~2022-06-08 11:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220608114548.25837-2-liudongdong3@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=20220608114650.DB550121D20@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=liudongdong3@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).