From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: ejnulak <luka.jankovic@ericsson.com>
Subject: |WARNING| pw152251 [PATCH v9 3/3] eventdev: add atomic atq to test-eventdev app
Date: Wed, 5 Mar 2025 15:15:05 +0100 (CET) [thread overview]
Message-ID: <20250305141505.379F41278BF@dpdk.org> (raw)
In-Reply-To: <20250305141255.3031686-4-luka.jankovic@ericsson.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152251
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#175: FILE: app/test-eventdev/test_atomic_atq.c:5:
+#include <stdio.h>
total: 0 errors, 1 warnings, 2003 lines checked
next prev parent reply other threads:[~2025-03-05 14:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250305141255.3031686-4-luka.jankovic@ericsson.com>
2025-03-05 13:39 ` |SUCCESS| pw152249-152251 " qemudev
2025-03-05 13:43 ` qemudev
2025-03-05 14:15 ` checkpatch [this message]
2025-03-05 14:51 ` |SUCCESS| pw152249-152251 [PATCH] [v9,3/3] eventdev: add atomic atq dpdklab
2025-03-05 15:00 ` dpdklab
2025-03-05 15:00 ` dpdklab
2025-03-05 15:01 ` dpdklab
2025-03-05 15:04 ` |SUCCESS| pw152251 [PATCH v9 3/3] eventdev: add atomic atq to test-eventdev app 0-day Robot
2025-03-05 15:06 ` |PENDING| pw152249-152251 [PATCH] [v9,3/3] eventdev: add atomic atq dpdklab
2025-03-05 15:09 ` |SUCCESS| " dpdklab
2025-03-05 15:13 ` dpdklab
2025-03-05 15:21 ` dpdklab
2025-03-05 15:24 ` |PENDING| " dpdklab
2025-03-05 15:24 ` |FAILURE| " dpdklab
2025-03-05 15:38 ` |SUCCESS| " dpdklab
2025-03-05 15:46 ` dpdklab
2025-03-05 16:05 ` dpdklab
2025-03-05 16:35 ` dpdklab
2025-03-05 17:19 ` dpdklab
2025-03-05 18:16 ` dpdklab
2025-03-05 19:57 ` dpdklab
2025-03-06 3:35 ` dpdklab
2025-03-06 3:45 ` dpdklab
2025-03-06 3:56 ` dpdklab
2025-03-06 4:08 ` dpdklab
2025-03-06 4:08 ` dpdklab
2025-03-06 4:14 ` dpdklab
2025-03-06 4:20 ` dpdklab
2025-03-06 4:37 ` dpdklab
2025-03-06 5:09 ` 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=20250305141505.379F41278BF@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).