From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-test-report] |WARNING| pw25580 [PATCH 03/22] cryptodev: remove opaque data pointer in crypto op
Date: Wed, 21 Jun 2017 17:48:31 +0200 (CEST) [thread overview]
Message-ID: <20170621154831.2BDC9916B@dpdk.org> (raw)
In-Reply-To: <20170621074731.45013-3-pablo.de.lara.guarch@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/25580
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#87: FILE: app/test-crypto-perf/cperf_test_latency.c:423:
+ priv_data = (struct priv_op_data *) (ops[i]->sym + 1);
WARNING:LONG_LINE: line over 90 characters
#88: FILE: app/test-crypto-perf/cperf_test_latency.c:424:
+ priv_data->result->status = ops_processed[i]->status;
WARNING:LONG_LINE: line over 90 characters
#101: FILE: app/test-crypto-perf/cperf_test_latency.c:458:
+ priv_data = (struct priv_op_data *) (ops[i]->sym + 1);
WARNING:LONG_LINE: line over 90 characters
#102: FILE: app/test-crypto-perf/cperf_test_latency.c:459:
+ priv_data->result->status = ops_processed[i]->status;
total: 0 errors, 4 warnings, 90 lines checked
parent reply other threads:[~2017-06-21 15:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170621074731.45013-3-pablo.de.lara.guarch@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=20170621154831.2BDC9916B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pablo.de.lara.guarch@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).