From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-test-report] |WARNING| pw62490 [RFC 1/4] cpu-crypto: Introduce basic data structures
Date: Tue, 5 Nov 2019 19:42:13 +0100 (CET) [thread overview]
Message-ID: <20191105184213.AC7FD1BF71@dpdk.org> (raw)
In-Reply-To: <20191105184122.15172-2-konstantin.ananyev@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/62490
_coding style issues_
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#70: FILE: lib/librte_cryptodev/rte_crypto_sym.h:29:
+/**
+ * Crypto IO Vector (in analogy with struct iovec)
total: 0 errors, 1 warnings, 103 lines checked
parent reply other threads:[~2019-11-05 18:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191105184122.15172-2-konstantin.ananyev@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=20191105184213.AC7FD1BF71@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.ananyev@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).