From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Subject: [dpdk-test-report] |WARNING| pw31290 [PATCH RFC] eventdev: add crypto adapter API header
Date: Thu, 9 Nov 2017 07:54:41 +0100 (CET) [thread overview]
Message-ID: <20171109065441.38EC91B3C7@dpdk.org> (raw)
In-Reply-To: <1510210453-61428-1-git-send-email-abhinandan.gujjar@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/31290
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#133: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:91:
+ /**
+ * @warning
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#147: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:105:
+ /**
+ * @warning
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#155: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:113:
+ /**< Start only Rx part of crypto adapter.
+ * Packets dequeued from cryptodev are new to eventdev and
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#156: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:114:
+ * events will be treated as RTE_EVENT_OP_NEW */
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#159: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:117:
+ /**< Start both Rx & Tx part of crypto adapter.
+ * Packet's event context will be retained and
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#160: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:118:
+ * event will be treated as RTE_EVENT_OP_FORWARD */
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#252: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:210:
+ /**<
+ * The metadata offset indicates the location of the
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#258: FILE: lib/librte_eventdev/rte_event_crypto_adapter.h:216:
+ /**<
+ * When queuing is set to RTE_EVENT_CRYPTO_ENQ_MULTI_EVENTQ
total: 0 errors, 8 warnings, 481 lines checked
parent reply other threads:[~2017-11-09 6:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1510210453-61428-1-git-send-email-abhinandan.gujjar@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=20171109065441.38EC91B3C7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=abhinandan.gujjar@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).