From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-test-report] |WARNING| pw23781 [PATCH 1/2] eal/ppc: fix mmap for memory initialization
Date: Thu, 20 Apr 2017 09:40:40 +0200 (CEST) [thread overview]
Message-ID: <20170420074040.047AF37B0@dpdk.org> (raw)
In-Reply-To: <8100178.UKWLChnxCa@xps>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/23781
_coding style issues_
WARNING:TYPO_SPELLING: 'initilization' may be misspelled - perhaps 'initialization'?
#18:
> the memory initilization for the second process fails. This patch adds
WARNING:TYPO_SPELLING: 'initilization' may be misspelled - perhaps 'initialization'?
#21:
> doing the initilization, users need to set both nr_hugepages and
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#62:
@@ -1359,7 +1365,13 @@ rte_eal_hugepage_attach(void)
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#63:
* use mmap to get identical addresses as the primary process.
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#85: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:333:
fd, 0);
ERROR:CODE_INDENT: code indent should use tabs where possible
#86: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:334:
+ (*size) + hugepage_sz, PROT_READ,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#86: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:334:
+ (*size) + hugepage_sz, PROT_READ,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#88: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:336:
+ MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:336:
+ MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#90: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:338:
+ MAP_PRIVATE,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#90: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:338:
+ MAP_PRIVATE,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#92: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:340:
+ fd, 0);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#92: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:340:
+ fd, 0);$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 7 errors, 7 warnings, 14 lines checked
parent reply other threads:[~2017-04-20 7:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8100178.UKWLChnxCa@xps>]
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=20170420074040.047AF37B0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).