automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Subject: [dpdk-test-report] |WARNING| [PATCH 2/2] app/crypto-perf: Introduce new performance test application
Date: Fri,  2 Dec 2016 16:17:05 +0100 (CET)	[thread overview]
Message-ID: <20161202151705.6229EFA4E@dpdk.org> (raw)
In-Reply-To: <1480691702-4600-3-git-send-email-michalx.k.jastrzebski@intel.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/17492

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#69: 
chained mbufs are processing in crypto device. “param” specify number of

WARNING:LONG_LINE: line over 90 characters
#1153: FILE: app/crypto-perf/cperf_options_parsing.c:296:
+			rte_crypto_cipher_algorithm_strings[RTE_CRYPTO_CIPHER_SNOW3G_UEA2],

total: 0 errors, 2 warnings, 3387 lines checked

           reply	other threads:[~2016-12-02 15:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1480691702-4600-3-git-send-email-michalx.k.jastrzebski@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=20161202151705.6229EFA4E@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=michalx.k.jastrzebski@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).