From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nitin Saxena <nsaxena@marvell.com>
Subject: |WARNING| pw149581 [PATCH v6 4/4] app/graph: add custom feature nodes for ip4 output arc
Date: Fri, 3 Jan 2025 07:07:14 +0100 (CET) [thread overview]
Message-ID: <20250103060714.16F29121D87@dpdk.org> (raw)
In-Reply-To: <20250103060612.2671836-5-nsaxena@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/149581
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#132: FILE: app/graph/feature.c:5:
+#include <stdio.h>
total: 0 errors, 1 warnings, 421 lines checked
next prev parent reply other threads:[~2025-01-03 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250103060612.2671836-5-nsaxena@marvell.com>
2025-01-03 5:35 ` |SUCCESS| pw149578-149581 " qemudev
2025-01-03 5:40 ` qemudev
2025-01-03 6:07 ` checkpatch [this message]
2025-01-03 7:05 ` |FAILURE| pw149581 " 0-day Robot
2025-01-03 8:12 ` |FAILURE| pw149578-149581 [PATCH] [v6, " 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=20250103060714.16F29121D87@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).