From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw21793 [PATCH v4 7/8] net/tap: add packet type management
Date: Wed, 15 Mar 2017 18:43:59 +0100 (CET) [thread overview]
Message-ID: <20170315174359.4E47C28F3@dpdk.org> (raw)
In-Reply-To: <725e6ac6-acc5-7adc-02a7-f1a6bf79f7bd@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/21793
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#24:
> @@ -228,6 +229,8 @@ pmd_rx_burst(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#44:
--- a/drivers/net/tap/Makefile
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 2 errors, 1 warnings, 0 checks, 6 lines checked
parent reply other threads:[~2017-03-15 17:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <725e6ac6-acc5-7adc-02a7-f1a6bf79f7bd@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=20170315174359.4E47C28F3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ferruh.yigit@intel.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).