From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: alok.makhariya@nxp.com
Subject: [dpdk-test-report] |WARNING| pw30287 [PATCH] crypto/dpaa_sec: add check for segmented buffer
Date: Thu, 12 Oct 2017 15:10:42 +0200 (CEST) [thread overview]
Message-ID: <20171012131042.293C81B2F2@dpdk.org> (raw)
In-Reply-To: <20171012130726.4332-1-alok.makhariya@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/30287
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#37: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:899:
+ if (!rte_pktmbuf_is_contiguous(op->sym->m_src)) {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#37: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:899:
+ if (!rte_pktmbuf_is_contiguous(op->sym->m_src)) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#38: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:900:
+ op->status = RTE_CRYPTO_OP_STATUS_ERROR;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#38: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:900:
+ op->status = RTE_CRYPTO_OP_STATUS_ERROR;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#39: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:901:
+ return -ENOTSUP;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#39: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:901:
+ return -ENOTSUP;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#40: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:902:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#40: FILE: drivers/crypto/dpaa_sec/dpaa_sec.c:902:
+ }$
total: 4 errors, 4 warnings, 13 lines checked
parent reply other threads:[~2017-10-12 13:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171012130726.4332-1-alok.makhariya@nxp.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=20171012131042.293C81B2F2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=alok.makhariya@nxp.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).