From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shally Verma <shally.verma@caviumnetworks.com>
Subject: [dpdk-test-report] |WARNING| pw34308 [PATCH RFC v1 1/1] lib/cryptodev: add support of asymmetric crypto
Date: Tue, 23 Jan 2018 10:55:48 +0100 (CET) [thread overview]
Message-ID: <20180123095548.E26131B1A8@dpdk.org> (raw)
In-Reply-To: <1516701263-13154-2-git-send-email-shally.verma@caviumnetworks.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/34308
_coding style issues_
WARNING:TYPO_SPELLING: 'informations' may be misspelled - perhaps 'information'?
#24:
data and other informations
WARNING:TYPO_SPELLING: 'algoritms' may be misspelled - perhaps 'algorithms'?
#48:
Other algoritms to be added in subsequent versions.
ERROR:TRAILING_WHITESPACE: trailing whitespace
#910: FILE: lib/librte_cryptodev/rte_crypto_asym.h:613:
+/** $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#1139: FILE: lib/librte_cryptodev/rte_crypto_asym.h:842:
+^I * $
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#2256: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:339:
+ struct rte_cryptodev *dev, unsigned nb_objs,
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#2257: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:340:
+ unsigned obj_cache_size, int socket_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#2274: FILE: lib/librte_cryptodev/rte_cryptodev_pmd.h:362:
+typedef unsigned (*cryptodev_asym_get_session_private_size_t)(
total: 2 errors, 5 warnings, 2173 lines checked
parent reply other threads:[~2018-01-23 9:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1516701263-13154-2-git-send-email-shally.verma@caviumnetworks.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=20180123095548.E26131B1A8@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=shally.verma@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).