From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Usman Tanveer <usman.tanveer@emumba.com>
Subject: |WARNING| pw117099 [PATCH v2] net/bonding: fix error in bonding mode 4 with dedicated queues enabled
Date: Thu, 29 Sep 2022 06:07:32 +0200 (CEST) [thread overview]
Message-ID: <20220929040732.9736A12231E@dpdk.org> (raw)
In-Reply-To: <20220929040551.120717-1-usman.tanveer@emumba.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/117099
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#104: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1834:
+ errval = rte_eth_dev_start(slave_eth_dev->data->port_id);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#107: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1837:
+ slave_eth_dev->data->port_id, errval);
total: 0 errors, 2 warnings, 0 checks, 32 lines checked
next parent reply other threads:[~2022-09-29 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220929040551.120717-1-usman.tanveer@emumba.com>
2022-09-29 4:07 ` checkpatch [this message]
2022-09-29 5:19 ` |SUCCESS| " 0-day Robot
2022-09-29 8:58 |WARNING| pw117099 [PATCH] [v2] " 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=20220929040732.9736A12231E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=usman.tanveer@emumba.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).