automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Min Hu (Connor)" <humin29@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw104034 [PATCH] net/bonding: fix offloading configuration
Date: Tue,  9 Nov 2021 09:00:10 +0100 (CET)	[thread overview]
Message-ID: <20211109080010.68896123078@dpdk.org> (raw)
In-Reply-To: <20211109075726.59611-1-humin29@huawei.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/104034

_coding style issues_


WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#57: 
delivered to the slave devices in this way.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#60: 
the capability of all slave devices. Based on this, the following functions

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#63: 
all the slave devices support this Tx offloading), the enabling status of

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#64: 
the offloading of all slave devices depends on the configuration of the

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#68: 
of the bonding device, the enabling status of the offloading on the slave

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#70: 
on the original configuration of the slave devices.

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#100: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1719:
+	slave_eth_dev->data->dev_conf.txmode.offloads |=

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#103: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1722:
+	slave_eth_dev->data->dev_conf.txmode.offloads &=

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#107: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1726:
+	slave_eth_dev->data->dev_conf.rxmode.offloads |=

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#110: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1729:
+	slave_eth_dev->data->dev_conf.rxmode.offloads &=

total: 0 errors, 10 warnings, 0 checks, 32 lines checked

       reply	other threads:[~2021-11-09  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211109075726.59611-1-humin29@huawei.com>
2021-11-09  8:00 ` checkpatch [this message]
2021-11-09  8:39 ` [dpdk-test-report] |SUCCESS| pw104034 [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=20211109080010.68896123078@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=humin29@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).