From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Subject: [dpdk-test-report] |WARNING| [PATCH 4/4] test: add sgl unit tests for crypto devices
Date: Fri, 2 Dec 2016 18:08:18 +0100 (CET) [thread overview]
Message-ID: <20161202170818.3E1B8FA47@dpdk.org> (raw)
In-Reply-To: <1480698466-17620-5-git-send-email-tomaszx.kulasek@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/17499
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#82: FILE: app/test/test_cryptodev.c:2523:
+ unsigned plaintext_pad_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#83: FILE: app/test/test_cryptodev.c:2524:
+ unsigned plaintext_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#166: FILE: app/test/test_cryptodev.c:2668:
+ unsigned plaintext_pad_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#167: FILE: app/test/test_cryptodev.c:2669:
+ unsigned plaintext_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#249: FILE: app/test/test_cryptodev.c:3016:
+ unsigned plaintext_pad_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#250: FILE: app/test/test_cryptodev.c:3017:
+ unsigned plaintext_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#335: FILE: app/test/test_cryptodev.c:3750:
+ unsigned plaintext_pad_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#336: FILE: app/test/test_cryptodev.c:3751:
+ unsigned plaintext_len;
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#471: FILE: app/test/test_cryptodev.c:4433:
+ unsigned plaintext_len;
total: 0 errors, 9 warnings, 954 lines checked
parent reply other threads:[~2016-12-02 17:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1480698466-17620-5-git-send-email-tomaszx.kulasek@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=20161202170818.3E1B8FA47@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=tomaszx.kulasek@intel.com \
/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).