From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-test-report] |WARNING| pw51276 [PATCH v2 3/4] crypto/qat: add modular exponentiation to qat asym pmd
Date: Mon, 18 Mar 2019 13:47:31 +0100 (CET) [thread overview]
Message-ID: <20190318124731.32F854CC0@dpdk.org> (raw)
In-Reply-To: <20190318124515.4660-4-arkadiuszx.kusztal@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/51276
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#19:
driver. For capabilities or limitations refer to qat.rst or qat_asym_capabilities.h.
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#66: FILE: drivers/crypto/qat/qat_asym.c:14:
+static int qat_asym_get_sz_and_func_id(const uint32_t arr[][2],
size_t arr_sz, size_t *size, uint32_t *func_id) {
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#100: FILE: drivers/crypto/qat/qat_asym.c:76:
+static void qat_clear_arrays(struct qat_asym_op_cookie *cookie, int in_count,
int out_count, int in_size, int out_size) {
WARNING:LONG_LINE: line over 90 characters
#224: FILE: drivers/crypto/qat/qat_asym.c:241:
+ (asym_op->modex.result.length - ctx->sess_alg_params.mod_exp.n.length),
WARNING:LONG_LINE: line over 90 characters
#267: FILE: drivers/crypto/qat/qat_asym.c:285:
+ if (xform->modex.exponent.length == 0 || xform->modex.modulus.length == 0) {
total: 2 errors, 3 warnings, 273 lines checked
parent reply other threads:[~2019-03-18 12:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190318124515.4660-4-arkadiuszx.kusztal@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=20190318124731.32F854CC0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=arkadiuszx.kusztal@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).