From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: chengtcli@qq.com
Subject: |WARNING| pw115556 [PATCH] eal: zero out new added memory
Date: Sat, 27 Aug 2022 11:27:58 +0200 (CEST) [thread overview]
Message-ID: <20220827092758.98621121DAD@dpdk.org> (raw)
In-Reply-To: <tencent_F3597A23B9EE72C7633E44F78D66D01F1109@qq.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/115556
_coding style issues_
WARNING:TYPO_SPELLING: 'doens' may be misspelled - perhaps 'does'?
#66:
When RTE_MALLOC_DEBUG not configured, rte_zmalloc_socket() doens't
WARNING:TYPO_SPELLING: 'allocaed' may be misspelled - perhaps 'allocated'?
#67:
zero oute allocaed memory. Because memory are zeroed out when free
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
WARNING:FUNCTION_ARGUMENTS: function definition argument 'elem' should also have an identifier name
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
WARNING:FUNCTION_ARGUMENTS: function definition argument 'heap' should also have an identifier name
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
WARNING:FUNCTION_ARGUMENTS: function definition argument 'msl' should also have an identifier name
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
WARNING:FUNCTION_ARGUMENTS: function definition argument 'len' should also have an identifier name
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
WARNING:FUNCTION_ARGUMENTS: function definition argument 'elem' should also have an identifier name
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
WARNING:FUNCTION_ARGUMENTS: function definition argument 'len' should also have an identifier name
#106: FILE: lib/librte_eal/common/malloc_heap.c:100:
+ size_t data_len
total: 0 errors, 9 warnings, 19 lines checked
next parent reply other threads:[~2022-08-27 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_F3597A23B9EE72C7633E44F78D66D01F1109@qq.com>
2022-08-27 9:27 ` checkpatch [this message]
2022-08-27 9:39 dpdklab
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=20220827092758.98621121DAD@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=chengtcli@qq.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).