From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nitin Saxena <nsaxena@marvell.com>
Subject: |WARNING| pw154071 [PATCH v12 7/7] test/graph_feature_arc: add functional tests
Date: Thu, 5 Jun 2025 19:34:41 +0200 (CEST) [thread overview]
Message-ID: <20250605173441.B789A125280@dpdk.org> (raw)
In-Reply-To: <20250605173315.1447003-8-nsaxena@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154071
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#135: FILE: app/test/test_graph_feature_arc.c:11:
+#include <stdio.h>
total: 0 errors, 1 warnings, 1381 lines checked
next prev parent reply other threads:[~2025-06-05 17:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250605173315.1447003-8-nsaxena@marvell.com>
2025-06-05 17:07 ` |SUCCESS| pw154065-154071 " qemudev
2025-06-05 17:11 ` qemudev
2025-06-05 17:34 ` checkpatch [this message]
2025-06-05 18:43 ` |SUCCESS| pw154065-154071 [PATCH] [v12,7/7] test/graph_feature_arc: dpdklab
2025-06-05 18:45 ` |SUCCESS| pw154071 [PATCH v12 7/7] test/graph_feature_arc: add functional tests 0-day Robot
2025-06-05 18:45 ` |SUCCESS| pw154065-154071 [PATCH] [v12,7/7] test/graph_feature_arc: dpdklab
2025-06-05 18:58 ` |PENDING| " dpdklab
2025-06-05 19:04 ` |SUCCESS| " dpdklab
2025-06-05 19:06 ` dpdklab
2025-06-05 19:13 ` |PENDING| " dpdklab
2025-06-05 19:18 ` |SUCCESS| " dpdklab
2025-06-05 19:18 ` |PENDING| " dpdklab
2025-06-05 21:48 ` |SUCCESS| " dpdklab
2025-06-05 23:37 ` |PENDING| " dpdklab
2025-06-05 23:51 ` |SUCCESS| " dpdklab
2025-06-05 23:52 ` dpdklab
2025-06-05 23:53 ` dpdklab
2025-06-05 23:54 ` dpdklab
2025-06-05 23:55 ` dpdklab
2025-06-05 23:56 ` dpdklab
2025-06-05 23:57 ` dpdklab
2025-06-05 23:57 ` dpdklab
2025-06-06 0:17 ` |PENDING| " dpdklab
2025-06-06 0:27 ` |WARNING| " dpdklab
2025-06-06 3:01 ` |SUCCESS| " dpdklab
2025-06-06 8:26 ` dpdklab
2025-06-06 11:18 ` dpdklab
2025-06-06 11:18 ` dpdklab
2025-06-06 11:21 ` dpdklab
2025-06-06 11: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=20250605173441.B789A125280@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nsaxena@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).