From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw39416 [PATCH v3 1/5] eventdev: introduce event crypto adapter
Date: Mon, 7 May 2018 11:36:22 +0200 (CEST) [thread overview]
Message-ID: <20180507093622.7E66A3195@dpdk.org> (raw)
In-Reply-To: <20180507093516.GA8052@jerin>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39416
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#30:
> lib/librte_eventdev/rte_event_crypto_adapter.h | 554 +++++++++++++++++++++++++
ERROR:TRAILING_WHITESPACE: trailing whitespace
#197: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:246:
+^I * port and dequeues crypto request events in $
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 2 errors, 1 warnings, 112 lines checked
parent reply other threads:[~2018-05-07 9:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180507093516.GA8052@jerin>]
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=20180507093622.7E66A3195@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).