From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: chenchanghu <chenchanghu@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw27248 [PATCH disscussion] mlx4 driver MLX4_PMD_TX_MP_CACHE default vaule
Date: Fri, 28 Jul 2017 10:00:16 +0200 (CEST) [thread overview]
Message-ID: <20170728080016.1DC439171@dpdk.org> (raw)
In-Reply-To: <859E1CB9FBF08C4B839DCF451B09C5032D62BFA3@dggeml505-mbx.china.huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/27248
_coding style issues_
WARNING:TYPO_SPELLING: 'vaule' may be misspelled - perhaps 'value'?
#5:
Subject: [dpdk-dev] [PATCH disscussion] mlx4 driver MLX4_PMD_TX_MP_CACHE default vaule
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#20:
When I used the mlx4 pmd, I meet a problem about MLX4_PMD_TX_MP_CACHE vaule, which is used for Memory pool to Memory region translation. The detail test is descripted below.
WARNING:TYPO_SPELLING: 'vaule' may be misspelled - perhaps 'value'?
#20:
When I used the mlx4 pmd, I meet a problem about MLX4_PMD_TX_MP_CACHE vaule, which is used for Memory pool to Memory region translation. The detail test is descripted below.
WARNING:TYPO_SPELLING: 'infomation' may be misspelled - perhaps 'information'?
#21:
1.Test environmemt infomation:
WARNING:TYPO_SPELLING: 'vaule' may be misspelled - perhaps 'value'?
#56:
c. Then we modify the MLX4_PMD_TX_MP_CACHE vaule to 32, which is configured the vaule 'CONFIG_RTE_LIBRTE_MLX4_TX_MP_CACHE' in the config/common_base file, we found the function 'rte_eth_tx_burst' running time is less than 5ms.
WARNING:TYPO_SPELLING: 'vaule' may be misspelled - perhaps 'value'?
#56:
c. Then we modify the MLX4_PMD_TX_MP_CACHE vaule to 32, which is configured the vaule 'CONFIG_RTE_LIBRTE_MLX4_TX_MP_CACHE' in the config/common_base file, we found the function 'rte_eth_tx_burst' running time is less than 5ms.
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#68: FILE: config/common_base:206:
CONFIG_RTE_LIBRTE_MLX4_DEBUG=n
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 2 errors, 6 warnings, 7 lines checked
parent reply other threads:[~2017-07-28 8:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <859E1CB9FBF08C4B839DCF451B09C5032D62BFA3@dggeml505-mbx.china.huawei.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=20170728080016.1DC439171@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chenchanghu@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).