From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Zhao, Bing" <ilovethull@163.com>
Subject: [dpdk-test-report] |WARNING| pw36909 [PATCH pktgen] Fix the "rte_memcpy" compiling on aarch64 platform
Date: Tue, 3 Apr 2018 08:37:24 +0200 (CEST) [thread overview]
Message-ID: <20180403063724.2413B1B676@dpdk.org> (raw)
In-Reply-To: <20180403063553.19852-1-ilovethull@163.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/36909
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#16:
The "rte_memcpy" will be a macro but not a function on aarch64 platform if the flags are not enabled (latest version). In old versions, it will always be a macro to memcpy.
ERROR:SPACING: space required before the open parenthesis '('
#51: FILE: app/cli-functions.c:918:
+ for(i = 0; i < cnt; i++)
ERROR:ELSE_AFTER_BRACE: else should follow close brace '}'
#54: FILE: app/cli-functions.c:921:
+ }
+ else {
ERROR:SPACING: space required before the open parenthesis '('
#55: FILE: app/cli-functions.c:922:
+ for(i = 0; i < cnt; i++)
total: 3 errors, 1 warnings, 28 lines checked
parent reply other threads:[~2018-04-03 6:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180403063553.19852-1-ilovethull@163.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=20180403063724.2413B1B676@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ilovethull@163.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).