From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chaoyong He <chaoyong.he@corigine.com>
Subject: |WARNING| pw128362 [PATCH] net/bonding: fix destroy dedicated queues flow
Date: Thu, 8 Jun 2023 05:00:33 +0200 (CEST) [thread overview]
Message-ID: <20230608030033.251AE12077C@dpdk.org> (raw)
In-Reply-To: <20230608025903.814504-1-chaoyong.he@corigine.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/128362
_coding style issues_
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#132:
maybe we couldn't add the member port to a new bonding
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#160: FILE: drivers/net/bonding/rte_eth_bond_api.c:718:
+ internals->mode4.dedicated_queues.flow[slave_port_id] != NULL) {
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#161: FILE: drivers/net/bonding/rte_eth_bond_api.c:719:
+ rte_flow_destroy(slave_port_id,
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#162: FILE: drivers/net/bonding/rte_eth_bond_api.c:720:
+ internals->mode4.dedicated_queues.flow[slave_port_id],
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#164: FILE: drivers/net/bonding/rte_eth_bond_api.c:722:
+ internals->mode4.dedicated_queues.flow[slave_port_id] = NULL;
total: 0 errors, 5 warnings, 0 checks, 16 lines checked
next prev parent reply other threads:[~2023-06-08 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230608025903.814504-1-chaoyong.he@corigine.com>
2023-06-08 2:48 ` |SUCCESS| " qemudev
2023-06-08 2:52 ` qemudev
2023-06-08 3:00 ` checkpatch [this message]
2023-06-08 4:19 ` 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=20230608030033.251AE12077C@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).