From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw31752 [PATCH RFC] eventdev: add crypto adapter API header
Date: Wed, 29 Nov 2017 12:43:54 +0100 (CET) [thread overview]
Message-ID: <20171129114354.7ACB13237@dpdk.org> (raw)
In-Reply-To: <20171129114153.GA16467@jerin>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/31752
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#33:
> lib/librte_eventdev/rte_event_crypto_adapter.h | 474 +++++++++++++++++++++++++
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#223: FILE: lib/librte_cryptodev/rte_crypto.h:120:
+ Crypto completion event attribute. For _session less_ crypto enqueue operation,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#224: FILE: lib/librte_cryptodev/rte_crypto.h:121:
+ The will field shall be used by application to post the crypto completion event$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#225: FILE: lib/librte_cryptodev/rte_crypto.h:122:
+ upon the crypto enqueue operation complete.$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#251: FILE: lib/librte_cryptodev/rte_cryptodev.h:949:
+ Create PMD specific session meta data for the destination event queue$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#252: FILE: lib/librte_cryptodev/rte_cryptodev.h:950:
+ attribute to post the crypto completion event on crypto work complete.$
ERROR:CODE_INDENT: code indent should use tabs where possible
#256: FILE: lib/librte_cryptodev/rte_cryptodev.h:954:
+ struct rte_cryptodev_sym_session *sess,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#256: FILE: lib/librte_cryptodev/rte_cryptodev.h:954:
+ struct rte_cryptodev_sym_session *sess,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#257: FILE: lib/librte_cryptodev/rte_cryptodev.h:955:
+ struct rte_crypto_sym_xform *xforms,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#257: FILE: lib/librte_cryptodev/rte_cryptodev.h:955:
+ struct rte_crypto_sym_xform *xforms,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#258: FILE: lib/librte_cryptodev/rte_cryptodev.h:956:
+ struct rte_mempool *mempool,$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#258: FILE: lib/librte_cryptodev/rte_cryptodev.h:956:
+ struct rte_mempool *mempool,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#259: FILE: lib/librte_cryptodev/rte_cryptodev.h:957:
+ struct rte_event ev);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#259: FILE: lib/librte_cryptodev/rte_cryptodev.h:957:
+ struct rte_event ev);$
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 5 errors, 10 warnings, 22 lines checked
parent reply other threads:[~2017-11-29 11:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171129114153.GA16467@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=20171129114354.7ACB13237@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).