From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Huisong Li <lihuisong@huawei.com>
Subject: |WARNING| pw119243 [PATCH] app/testpmd: update bond port configurations when add slave
Date: Fri, 28 Oct 2022 05:54:02 +0200 (CEST) [thread overview]
Message-ID: <20221028035402.CD5EB122B86@dpdk.org> (raw)
In-Reply-To: <20221028035331.49406-1-lihuisong@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/119243
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#35:
Subject: [PATCH] app/testpmd: update bond port configurations when add slave
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#58:
bonding device in dev_info is zero when no slave is added. And its
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#59:
capability will be updated when add a new slave device.
WARNING:TYPO_SPELLING: 'probelms' may be misspelled - perhaps 'problems'?
#61:
The capability to update dynamically can introduce some probelms if
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#70:
intersection of the capability of all slave devices. If use original port
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#71:
configurations, the removed capabilities because of adding a new slave may
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#95: FILE: app/test-pmd/testpmd.c:2810:
+ * device in dev_info is zero when no slave is added. And its capability of
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#96: FILE: app/test-pmd/testpmd.c:2811:
+ * will be updated when add a new slave device. So adding a device slave need
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#96: FILE: app/test-pmd/testpmd.c:2811:
+ * will be updated when add a new slave device. So adding a device slave need
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#165: FILE: drivers/net/bonding/bonding_testpmd.c:628:
+ ports[master_port_id].update_conf = 1;
total: 0 errors, 10 warnings, 0 checks, 75 lines checked
next parent reply other threads:[~2022-10-28 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221028035331.49406-1-lihuisong@huawei.com>
2022-10-28 3:54 ` checkpatch [this message]
2022-10-28 4:59 ` |SUCCESS| " 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=20221028035402.CD5EB122B86@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=lihuisong@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).