From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Peng Zhihong <zhihongx.peng@intel.com>
Subject: [dpdk-test-report] |WARNING| pw85444 [RFC] mem_debug add more log
Date: Fri, 18 Dec 2020 11:32:20 +0100 (CET) [thread overview]
Message-ID: <20201218103220.193CFCAAE@dpdk.org> (raw)
In-Reply-To: <20201218192109.50098-1-zhihongx.peng@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/85444
_coding style issues_
WARNING:TYPO_SPELLING: 'memeory' may be misspelled - perhaps 'memory'?
#60:
a) When a memeory overlflow occur in rte_free, there is a little log
WARNING:TYPO_SPELLING: 'overlflow' may be misspelled - perhaps 'overflow'?
#60:
a) When a memeory overlflow occur in rte_free, there is a little log
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#67:
is not released and an overflow is occured and also the second block
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#68:
of memory is covered, a memory overflow will be detected once the second
WARNING:TYPO_SPELLING: 'funcation' may be misspelled - perhaps 'function'?
#96:
memory on the list. Call this funcation manually at the exit
WARNING:TYPO_SPELLING: 'erro' may be misspelled - perhaps 'error'?
#266: FILE: lib/librte_eal/common/rte_malloc.c:726:
+ printf("%s mallco te erro.
", __func__);
WARNING:TYPO_SPELLING: 'erro' may be misspelled - perhaps 'error'?
#273: FILE: lib/librte_eal/common/rte_malloc.c:733:
+ printf("%s mallco debug_info erro.
", __func__);
WARNING:TYPO_SPELLING: 'erro' may be misspelled - perhaps 'error'?
#280: FILE: lib/librte_eal/common/rte_malloc.c:740:
+ printf("%s mallco file erro.
", __func__);
WARNING:TYPO_SPELLING: 'erro' may be misspelled - perhaps 'error'?
#286: FILE: lib/librte_eal/common/rte_malloc.c:746:
+ printf("%s mallco func erro.
", __func__);
total: 0 errors, 9 warnings, 593 lines checked
ERROR: symbol rte_calloc_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_calloc_socket_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_malloc_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_malloc_socket_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_malloc_validate_all_memory is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_malloc_debug_read_lock is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_malloc_debug_read_unlock is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_malloc_debug_write_lock is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mcfg_malloc_debug_write_unlock is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_realloc_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
INFO: symbol rte_realloc_socket_debug has been added to the EXPERIMENTAL section of the version map
ERROR: symbol rte_zmalloc_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_zmalloc_socket_debug is added in the DPDK_21 section, but is expected to be added in the EXPERIMENTAL section of the version map
parent reply other threads:[~2020-12-18 10:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201218192109.50098-1-zhihongx.peng@intel.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=20201218103220.193CFCAAE@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=zhihongx.peng@intel.com \
/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).