From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: yuan peng <yuan.peng@intel.com>
Subject: [dpdk-test-report] |WARNING| pw22035 [PATCH v4 2/2] app/test: add unit test for CRC computation
Date: Wed, 22 Mar 2017 08:16:18 +0100 (CET) [thread overview]
Message-ID: <20170322071618.E2C40133F@dpdk.org> (raw)
In-Reply-To: <67D543A150B29E4CAAE53918F64EDAEA3738A761@SHSMSX103.ccr.corp.intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/22035
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#18:
The second patch cannot be applied, since the test folder has moved to the DPDK root directory.
ERROR:TRAILING_WHITESPACE: trailing whitespace
#128: FILE: app/test/test_crc.c:71:
+uint32_t crc32_vec_res, crc32_vec1_res, crc32_vec2_res; uint32_t $
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#281: FILE: app/test/test_crc.c:222:
2.5.5
total: 2 errors, 1 warnings, 232 lines checked
parent reply other threads:[~2017-03-22 7:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <67D543A150B29E4CAAE53918F64EDAEA3738A761@SHSMSX103.ccr.corp.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=20170322071618.E2C40133F@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=yuan.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).