From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw97246 [RFC 07/15] eventdev: make drivers to use new API
Date: Mon, 23 Aug 2021 21:41:35 +0200 (CEST) [thread overview]
Message-ID: <20210823194135.74FE01226B3@dpdk.org> (raw)
In-Reply-To: <20210823194020.1229-7-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/97246
_coding style issues_
WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#2861: FILE: drivers/event/octeontx2/otx2_evdev.h:307:
+#define R(name, f6, f5, f4, f3, f2, f1, f0, flags) \
+ uint16_t otx2_ssogws_deq_##name(uint8_t dev_id, uint8_t port_id, \
+ struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_timeout_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_timeout_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_seg_##name(uint8_t dev_id, uint8_t port_id, \
+ struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_seg_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_seg_timeout_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_deq_seg_timeout_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
\
+ uint16_t otx2_ssogws_dual_deq_##name(uint8_t dev_id, uint8_t port_id, \
+ struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_timeout_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_timeout_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_seg_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_seg_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_seg_timeout_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event *ev, \
+ uint64_t timeout_ticks); \
+ uint16_t otx2_ssogws_dual_deq_seg_timeout_burst_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events, uint64_t timeout_ticks);
WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#2953: FILE: drivers/event/octeontx2/otx2_evdev.h:361:
+#define T(name, f6, f5, f4, f3, f2, f1, f0, sz, flags) \
+ uint16_t otx2_ssogws_tx_adptr_enq_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events); \
+ uint16_t otx2_ssogws_tx_adptr_enq_seg_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events); \
+ uint16_t otx2_ssogws_dual_tx_adptr_enq_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events); \
+ uint16_t otx2_ssogws_dual_tx_adptr_enq_seg_##name( \
+ uint8_t dev_id, uint8_t port_id, struct rte_event ev[], \
+ uint16_t nb_events);
total: 0 errors, 2 warnings, 3142 lines checked
parent reply other threads:[~2021-08-23 19:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210823194020.1229-7-pbhagavatula@marvell.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=20210823194135.74FE01226B3@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).