From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw97548 [PATCH 8/8] event/cnxk: add cn10k crypto adapter fast path ops
Date: Mon, 30 Aug 2021 13:12:28 +0200 (CEST) [thread overview]
Message-ID: <20210830111228.71D2E122CD1@dpdk.org> (raw)
In-Reply-To: <d368e3dc9ef492b6a82cddec03da6f4b832bff5a.1630315730.git.sthotton@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/97548
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#289: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:14:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#289: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:14:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#291: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:16:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#291: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:16:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#297: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:22:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#297: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:22:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#301: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:26:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#301: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:26:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#307: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:32:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#307: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:32:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#310: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:35:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#310: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:35:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#315: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:40:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#315: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:40:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#317: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:42:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#317: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:42:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#323: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:48:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#323: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:48:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#328: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:53:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#328: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:53:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#334: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:59:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#334: FILE: drivers/event/cnxk/cn10k_worker_deq_ca.c:59:
+ \$
total: 11 errors, 11 warnings, 222 lines checked
--- a/doc/guides/rel_notes/release_21_11.rst
+++ b/doc/guides/rel_notes/release_21_11.rst
next parent reply other threads:[~2021-08-30 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d368e3dc9ef492b6a82cddec03da6f4b832bff5a.1630315730.git.sthotton@marvell.com>
2021-08-30 11:12 ` checkpatch [this message]
2021-08-30 11:40 ` [dpdk-test-report] |SUCCESS| pw97548 [dpdk-dev] " 0-day Robot
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=20210830111228.71D2E122CD1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sthotton@marvell.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).