automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: ejnulak <luka.jankovic@ericsson.com>
Subject: |WARNING| pw149932 [RFC v3 1/1] eventdev: add atomic queue to test-eventdev app
Date: Mon, 13 Jan 2025 10:05:16 +0100 (CET)	[thread overview]
Message-ID: <20250113090516.D1B77126FD3@dpdk.org> (raw)
In-Reply-To: <20250113090451.2180161-1-luka.jankovic@ericsson.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/149932

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#113: 
Add an atomic queue test based on the order queue test but use exclusively atomic queues.

WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#184: FILE: app/test-eventdev/test_atomic_queue.c:2:
+#include <stdio.h>

ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#333: FILE: app/test-eventdev/test_atomic_queue.c:151:
+		uint32_t *const expected_flow_seq, RTE_ATOMIC(uint64_t) *const outstand_pkts,
 		                                                        ^

WARNING:BRACES: braces {} are not necessary for single statement blocks
#376: FILE: app/test-eventdev/test_atomic_queue.c:194:
+			if (!flow_id_cap) {
+				ev[i].flow_id = event_data_get_flow(&ev[i]);
+			}

WARNING:BRACES: braces {} are not necessary for single statement blocks
#544: FILE: app/test-eventdev/test_atomic_queue.c:362:
+	for (uint32_t i = 0; i < num_locks; i++) {
+		rte_spinlock_init(&atomic_locks[i]);
+	}

total: 1 errors, 4 warnings, 429 lines checked
Warning in app/test-eventdev/test_atomic_queue.c:
Using %l format, prefer %PRI*64 if type is [u]int64_t

  parent reply	other threads:[~2025-01-13  9:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250113090451.2180161-1-luka.jankovic@ericsson.com>
2025-01-13  8:33 ` |SUCCESS| " qemudev
2025-01-13  8:38 ` qemudev
2025-01-13  9:05 ` checkpatch [this message]
2025-01-13 10:06 ` |FAILURE| " 0-day Robot
2025-01-13 13:48 ` |PENDING| pw149932 [PATCH] [RFC,v3,1/1] eventdev: add atomic queue t dpdklab
2025-01-13 13:54 ` dpdklab
2025-01-13 13:57 ` dpdklab
2025-01-13 13:59 ` |SUCCESS| " dpdklab
2025-01-13 13:59 ` dpdklab
2025-01-13 14:01 ` |PENDING| " dpdklab
2025-01-13 14:03 ` |SUCCESS| " dpdklab
2025-01-13 14:04 ` dpdklab
2025-01-13 14:12 ` dpdklab
2025-01-13 14:14 ` |FAILURE| " dpdklab
2025-01-13 14:18 ` dpdklab
2025-01-13 14:20 ` |PENDING| " dpdklab
2025-01-13 14:26 ` |SUCCESS| " dpdklab
2025-01-13 14:26 ` |WARNING| " dpdklab
2025-01-13 14:27 ` |SUCCESS| " dpdklab
2025-01-13 14:31 ` |FAILURE| " dpdklab
2025-01-13 14:31 ` dpdklab
2025-01-13 14:32 ` dpdklab
2025-01-13 14:33 ` dpdklab
2025-01-13 14:34 ` dpdklab
2025-01-13 14:34 ` dpdklab
2025-01-13 14:36 ` dpdklab
2025-01-13 14:37 ` |WARNING| " dpdklab
2025-01-13 14:52 ` |SUCCESS| " dpdklab
2025-01-13 14:56 ` dpdklab
2025-01-13 14:57 ` |FAILURE| " dpdklab
2025-01-13 14:57 ` dpdklab
2025-01-13 17:06 ` dpdklab
2025-01-13 20:55 ` |SUCCESS| " 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=20250113090516.D1B77126FD3@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).