automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gaoxiang Liu <gaoxiangliu0@163.com>
Subject: |WARNING| pw108868 [PATCH v5] net/bonding: another fix to LACP mempool size
Date: Fri, 25 Mar 2022 13:11:43 +0100 (CET)	[thread overview]
Message-ID: <20220325121143.21279121D58@dpdk.org> (raw)
In-Reply-To: <20220325121023.746-1-gaoxiangliu0@163.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#60: 
The following log message may appear after a slave is idle(or nearly

WARNING:TYPO_SPELLING: 'chosed' may be misspelled - perhaps 'chose'?
#65: 
Problem:When bond mode 4 has been chosed and delicated queue has

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#66: 
not been enable, all mbufs from a slave' private pool(used

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#72: 
Solution: Ensure that each slave'tx (LACPDU) mempool owns more than

WARNING:TYPO_SPELLING: 'fuction' may be misspelled - perhaps 'function'?
#76: 
Note that the LACP tx machine fuction is the only code that allocates

WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#77: 
from a slave's private pool. It runs in the context of the interrupt

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#118: FILE: drivers/net/bonding/rte_eth_bond_8023ad.c:1105:
+ * CACHE_FLUSHTHRESH_MULTIPLIER already defined in rte_mempool.c */

WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Gaoxiang Liu <gaoxiangliu0@163.com>' != 'Signed-off-by: Gaoxiang Liu <liugaoxiang@huawei.com>'

total: 0 errors, 8 warnings, 0 checks, 25 lines checked

       reply	other threads:[~2022-03-25 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220325121023.746-1-gaoxiangliu0@163.com>
2022-03-25 12:11 ` checkpatch [this message]
2022-03-25 13:39 ` |FAILURE| " 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=20220325121143.21279121D58@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=gaoxiangliu0@163.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).