From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
Subject: [dpdk-test-report] |WARNING| pw94667 [PATCH 3/3] net/bonding: start ethdev prior to setting 8023ad flow
Date: Tue, 22 Jun 2021 11:26:27 +0200 (CEST) [thread overview]
Message-ID: <20210622092627.F023F122E3A@dpdk.org> (raw)
In-Reply-To: <20210622092531.73112-4-xhavli56@stud.fit.vutbr.cz>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/94667
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#59:
bond_ethdev_8023ad_flow_set(267) - bond_ethdev_8023ad_flow_set: port not started (slave_port=0 queue_id=1)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#59:
bond_ethdev_8023ad_flow_set(267) - bond_ethdev_8023ad_flow_set: port not started (slave_port=0 queue_id=1)
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#78: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1824:
+ errval = rte_eth_dev_start(slave_eth_dev->data->port_id);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#81: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1827:
+ slave_eth_dev->data->port_id, errval);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#94: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1840:
+ errval = rte_eth_dev_stop(slave_eth_dev->data->port_id);
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#98: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1844:
+ slave_eth_dev->data->port_id, errval);
total: 0 errors, 6 warnings, 0 checks, 43 lines checked
next parent reply other threads:[~2021-06-22 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210622092531.73112-4-xhavli56@stud.fit.vutbr.cz>
2021-06-22 9:26 ` checkpatch [this message]
2021-06-22 11:01 ` [dpdk-test-report] |SUCCESS| pw94667 [dpdk-dev] " 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=20210622092627.F023F122E3A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=xhavli56@stud.fit.vutbr.cz \
/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).