From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw93415 [PATCH v2 4/4] event/cnxk: add Tx adapter fastpath ops
Date: Mon, 24 May 2021 14:24:57 +0200 (CEST) [thread overview]
Message-ID: <20210524122457.5DE8E122E1E@dpdk.org> (raw)
In-Reply-To: <20210524122303.1116-4-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/93415
_coding style issues_
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#107: FILE: drivers/event/cnxk/cn10k_eventdev.c:348:
+ const event_tx_adapter_enqueue sso_hws_tx_adptr_enq_seg[2][2][2][2][2] =
+ {
ERROR:CODE_INDENT: code indent should use tabs where possible
#158: FILE: drivers/event/cnxk/cn10k_worker.c:185:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#158: FILE: drivers/event/cnxk/cn10k_worker.c:185:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#166: FILE: drivers/event/cnxk/cn10k_worker.c:193:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#166: FILE: drivers/event/cnxk/cn10k_worker.c:193:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#172: FILE: drivers/event/cnxk/cn10k_worker.c:199:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#172: FILE: drivers/event/cnxk/cn10k_worker.c:199:
+ \$
WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#252: FILE: drivers/event/cnxk/cn10k_worker.h:296:
+#define T(name, f4, f3, f2, f1, f0, sz, flags) \
+ uint16_t __rte_hot cn10k_sso_hws_tx_adptr_enq_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events); \
+ uint16_t __rte_hot cn10k_sso_hws_tx_adptr_enq_seg_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events); \
+ uint16_t __rte_hot cn10k_sso_hws_dual_tx_adptr_enq_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events); \
+ uint16_t __rte_hot cn10k_sso_hws_dual_tx_adptr_enq_seg_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events);
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#283: FILE: drivers/event/cnxk/cn9k_eventdev.c:439:
+ const event_tx_adapter_enqueue sso_hws_tx_adptr_enq_seg[2][2][2][2][2] =
+ {
ERROR:CODE_INDENT: code indent should use tabs where possible
#384: FILE: drivers/event/cnxk/cn9k_worker.c:386:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#384: FILE: drivers/event/cnxk/cn9k_worker.c:386:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#392: FILE: drivers/event/cnxk/cn9k_worker.c:394:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#392: FILE: drivers/event/cnxk/cn9k_worker.c:394:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#398: FILE: drivers/event/cnxk/cn9k_worker.c:400:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#398: FILE: drivers/event/cnxk/cn9k_worker.c:400:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#406: FILE: drivers/event/cnxk/cn9k_worker.c:408:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#406: FILE: drivers/event/cnxk/cn9k_worker.c:408:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#412: FILE: drivers/event/cnxk/cn9k_worker.c:414:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#412: FILE: drivers/event/cnxk/cn9k_worker.c:414:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#420: FILE: drivers/event/cnxk/cn9k_worker.c:422:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#420: FILE: drivers/event/cnxk/cn9k_worker.c:422:
+ \$
ERROR:CODE_INDENT: code indent should use tabs where possible
#426: FILE: drivers/event/cnxk/cn9k_worker.c:428:
+ \$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#426: FILE: drivers/event/cnxk/cn9k_worker.c:428:
+ \$
WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#526: FILE: drivers/event/cnxk/cn9k_worker.h:477:
+#define T(name, f4, f3, f2, f1, f0, sz, flags) \
+ uint16_t __rte_hot cn9k_sso_hws_tx_adptr_enq_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events); \
+ uint16_t __rte_hot cn9k_sso_hws_tx_adptr_enq_seg_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events); \
+ uint16_t __rte_hot cn9k_sso_hws_dual_tx_adptr_enq_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events); \
+ uint16_t __rte_hot cn9k_sso_hws_dual_tx_adptr_enq_seg_##name( \
+ void *port, struct rte_event ev[], uint16_t nb_events);
total: 12 errors, 12 warnings, 415 lines checked
next parent reply other threads:[~2021-05-24 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210524122303.1116-4-pbhagavatula@marvell.com>
2021-05-24 12:24 ` checkpatch [this message]
2021-05-24 13:59 ` [dpdk-test-report] |FAILURE| pw93415 [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=20210524122457.5DE8E122E1E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@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).