From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Luka Jankovic <luka.jankovic@ericsson.com>
Subject: |WARNING| pw149933 [RFC v4 1/1] eventdev: add atomic queue to test-eventdev app
Date: Mon, 13 Jan 2025 13:17:48 +0100 (CET) [thread overview]
Message-ID: <20250113121748.8BD6D126FBC@dpdk.org> (raw)
In-Reply-To: <20250113121733.2384990-1-luka.jankovic@ericsson.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/149933
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#110:
Add an atomic queue test based on the order queue test that exclusively uses atomic queues.
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#183: FILE: app/test-eventdev/test_atomic_queue.c:1:
+#include <stdio.h>
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#337: FILE: app/test-eventdev/test_atomic_queue.c:155:
+ RTE_ATOMIC(uint64_t) *const outstand_pkts,
^
WARNING:BRACES: braces {} are not necessary for single statement blocks
#381: FILE: app/test-eventdev/test_atomic_queue.c:199:
+ if (!flow_id_cap) {
+ ev[i].flow_id = event_data_get_flow(&ev[i]);
+ }
WARNING:BRACES: braces {} are not necessary for single statement blocks
#549: FILE: app/test-eventdev/test_atomic_queue.c:367:
+ for (uint32_t i = 0; i < num_locks; i++) {
+ rte_spinlock_init(&atomic_locks[i]);
+ }
total: 1 errors, 4 warnings, 434 lines checked
next prev parent reply other threads:[~2025-01-13 12:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250113121733.2384990-1-luka.jankovic@ericsson.com>
2025-01-13 11:47 ` |SUCCESS| " qemudev
2025-01-13 11:51 ` qemudev
2025-01-13 12:17 ` checkpatch [this message]
2025-01-13 12:48 ` |PENDING| pw149933 [PATCH] [RFC,v4,1/1] eventdev: add atomic queue t dpdklab
2025-01-13 12:53 ` dpdklab
2025-01-13 12:56 ` |SUCCESS| " dpdklab
2025-01-13 12:57 ` |PENDING| " dpdklab
2025-01-13 13:02 ` dpdklab
2025-01-13 13:03 ` |SUCCESS| " dpdklab
2025-01-13 13:08 ` dpdklab
2025-01-13 13:12 ` dpdklab
2025-01-13 13:12 ` |PENDING| " dpdklab
2025-01-13 13:14 ` |SUCCESS| " dpdklab
2025-01-13 13:17 ` |PENDING| " dpdklab
2025-01-13 13:22 ` |SUCCESS| " dpdklab
2025-01-13 13:25 ` |SUCCESS| pw149933 [RFC v4 1/1] eventdev: add atomic queue to test-eventdev app 0-day Robot
2025-01-13 13:25 ` |SUCCESS| pw149933 [PATCH] [RFC,v4,1/1] eventdev: add atomic queue t dpdklab
2025-01-13 13:28 ` dpdklab
2025-01-13 13:28 ` dpdklab
2025-01-13 13:31 ` dpdklab
2025-01-13 13:49 ` dpdklab
2025-01-13 13:50 ` dpdklab
2025-01-13 13:51 ` dpdklab
2025-01-13 14:39 ` |WARNING| " dpdklab
2025-01-13 14:49 ` |SUCCESS| " dpdklab
2025-01-13 14:51 ` dpdklab
2025-01-13 21:21 ` dpdklab
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=20250113121748.8BD6D126FBC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=luka.jankovic@ericsson.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).