From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gaoxiang Liu <gaoxiangliu0@163.com>
Subject: |WARNING| pw108534 [PATCH] net/bonding: another fix to LACP mempool size
Date: Fri, 4 Mar 2022 10:58:09 +0100 (CET) [thread overview]
Message-ID: <20220304095809.855FD12075F@dpdk.org> (raw)
In-Reply-To: <20220304095613.1717-1-gaoxiangliu0@163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/108534
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#58:
The following log message may appear after a slave is idle(or nearly
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#63:
Problem: All mbufs from a slave' private pool(used exclusively for
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#69:
Solution: Ensure that each slave'tx (LACPDU) mempool owns more than
WARNING:TYPO_SPELLING: 'fuction' may be misspelled - perhaps 'function'?
#73:
Note that the LACP tx machine fuction is the only code that allocates
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#74:
from a slave's private pool. It runs in the context of the interrupt
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, 6 warnings, 0 checks, 16 lines checked
next parent reply other threads:[~2022-03-04 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220304095613.1717-1-gaoxiangliu0@163.com>
2022-03-04 9:58 ` checkpatch [this message]
2022-03-04 11:38 ` |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=20220304095809.855FD12075F@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).