From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Robert Sanford <rsanford2@gmail.com>
Subject: |WARNING| pw105148 [PATCH 2/7] net/bonding: fix bonded dev configuring slave dev
Date: Wed, 15 Dec 2021 19:22:09 +0100 (CET) [thread overview]
Message-ID: <20211215182209.319BC12353F@dpdk.org> (raw)
In-Reply-To: <1639592401-56845-3-git-send-email-rsanford@akamai.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/105148
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#57:
Subject: [PATCH 2/7] net/bonding: fix bonded dev configuring slave dev
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#76:
- Replace directly overwriting of slave port's private rte_eth_conf
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#100: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1702:
+ /* Start with a copy of slave's current rte_eth_conf. */
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#101: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1703:
+ dev_conf = slave_eth_dev->data->dev_conf;
ERROR:TRAILING_WHITESPACE: trailing whitespace
#107: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1707:
+^Idev_conf.intr_conf.lsc = $
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#108: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1708:
+ (slave_eth_dev->data->dev_flags & RTE_ETH_DEV_INTR_LSC) ? 1 : 0;
WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Robert Sanford <rsanford2@gmail.com>' != 'Signed-off-by: Robert Sanford <rsanford@akamai.com>'
total: 1 errors, 6 warnings, 0 checks, 64 lines checked
parent reply other threads:[~2021-12-15 18:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1639592401-56845-3-git-send-email-rsanford@akamai.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=20211215182209.319BC12353F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rsanford2@gmail.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).