From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Lilijun <jerry.lilijun@huawei.com>
Subject: [dpdk-test-report] |WARNING| pw50978 [PATCH] eal: unmap unneed dpdk VA spaces for legacy mem
Date: Fri, 8 Mar 2019 06:41:17 +0100 (CET) [thread overview]
Message-ID: <20190308054117.A95E44C8F@dpdk.org> (raw)
In-Reply-To: <20190308053859.19980-1-jerry.lilijun@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/50978
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#17:
Comparing dpdk VA spaces to dpdk 16.11, the dpdk app process's VA spaces increase to above 30G.
WARNING:LONG_LINE: line over 90 characters
#40: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:1635:
+ void *va = (void*)((char*)msl->base_va + idx * msl->page_sz);
ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#40: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:1635:
+ void *va = (void*)((char*)msl->base_va + idx * msl->page_sz);
ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#40: FILE: lib/librte_eal/linuxapp/eal/eal_memory.c:1635:
+ void *va = (void*)((char*)msl->base_va + idx * msl->page_sz);
total: 2 errors, 2 warnings, 20 lines checked
parent reply other threads:[~2019-03-08 5:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190308053859.19980-1-jerry.lilijun@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=20190308054117.A95E44C8F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jerry.lilijun@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).