From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andy Green <andy@warmcat.com>
Subject: [dpdk-test-report] |WARNING| pw39716 [PATCH v3 00/40] Fix build on gcc8 and various bugs
Date: Thu, 10 May 2018 09:13:01 +0200 (CEST) [thread overview]
Message-ID: <20180510071301.F33D61B980@dpdk.org> (raw)
In-Reply-To: <2aa359ce-9441-7c9c-4492-8546bd6568ea@warmcat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39716
_coding style issues_
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#46:
8ea41438832a360aed2b7ba49fb75e310a2ff1dc
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#53:
> between incompatible function types from ‘int (* (*)(struct rte_pipeline
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#134:
@@ -105,7 +105,7 @@ rte_pipeline_table_action_handler_miss
ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#257: FILE: test/test/test_table_pipeline.c:70:
rte_mbuf **pkts,
ERROR:TRAILING_WHITESPACE: trailing whitespace
#263: FILE: test/test/test_table_pipeline.c:74:
+ uint64_t pkts_mask, struct rte_pipeline_table_entry *entry, void $
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#263: FILE: test/test/test_table_pipeline.c:74:
+ uint64_t pkts_mask, struct rte_pipeline_table_entry *entry, void $
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 5 errors, 2 warnings, 8 lines checked
parent reply other threads:[~2018-05-10 7:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2aa359ce-9441-7c9c-4492-8546bd6568ea@warmcat.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=20180510071301.F33D61B980@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andy@warmcat.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).