From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: scott.k.mitch1@gmail.com
Subject: |WARNING| pw159632 [PATCH v2 1/1] net: optimize raw checksum computation
Date: Wed, 7 Jan 2026 09:57:44 +0100 (CET) [thread overview]
Message-ID: <20260107085744.24AA9123FA0@dpdk.org> (raw)
In-Reply-To: <20260106210303.16008-1-scott.k.mitch1@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159632
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#142: FILE: app/test/test_cksum_fuzz.c:5:
+#include <stdio.h>
^^^^^
total: 0 errors, 1 warnings, 326 lines checked
next parent reply other threads:[~2026-01-07 8:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260106210303.16008-1-scott.k.mitch1@gmail.com>
2026-01-07 8:57 ` checkpatch [this message]
2026-01-07 9:46 ` |FAILURE| " 0-day Robot
2026-01-07 11:07 ` |SUCCESS| " qemudev
2026-01-07 11:12 ` qemudev
2026-01-07 15:56 ` |SUCCESS| pw159632 [PATCH] [v2,1/1] net: optimize raw checksum compu dpdklab
2026-01-07 15:57 ` |FAILURE| " dpdklab
2026-01-07 15:57 ` dpdklab
2026-01-07 15:58 ` |SUCCESS| " dpdklab
2026-01-07 16:01 ` |PENDING| " dpdklab
2026-01-07 16:02 ` dpdklab
2026-01-07 16:08 ` |FAILURE| " dpdklab
2026-01-07 16:08 ` dpdklab
2026-01-07 16:11 ` dpdklab
2026-01-07 16:20 ` |SUCCESS| " dpdklab
2026-01-07 16:20 ` dpdklab
2026-01-07 16:30 ` |FAILURE| " dpdklab
2026-01-07 16:31 ` |PENDING| " dpdklab
2026-01-07 17:26 ` |WARNING| " dpdklab
2026-01-07 18:14 ` dpdklab
2026-01-07 22:01 ` |SUCCESS| " dpdklab
2026-01-08 1:03 ` dpdklab
2026-01-08 2:26 ` |FAILURE| " dpdklab
2026-01-08 21:42 ` |SUCCESS| " dpdklab
2026-01-08 21:44 ` |FAILURE| " dpdklab
2026-01-08 21:55 ` dpdklab
2026-01-08 21:58 ` |SUCCESS| " dpdklab
2026-01-08 22:19 ` dpdklab
2026-01-08 22:24 ` |FAILURE| " dpdklab
2026-01-08 22:26 ` |SUCCESS| " dpdklab
2026-01-08 22:43 ` 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=20260107085744.24AA9123FA0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=scott.k.mitch1@gmail.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).