automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: scott.k.mitch1@gmail.com
Subject: |WARNING| pw159636 [PATCH v3] net: optimize raw checksum computation
Date: Wed,  7 Jan 2026 18:05:12 +0100 (CET)	[thread overview]
Message-ID: <20260107170512.058FF123FA0@dpdk.org> (raw)
In-Reply-To: <20260107170415.80275-1-scott.k.mitch1@gmail.com>

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

_coding style issues_

Must be a reply to the first patch (--in-reply-to).


WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#150: FILE: app/test/test_cksum_fuzz.c:5:
+#include <stdio.h>
           ^^^^^

total: 0 errors, 1 warnings, 353 lines checked

  parent reply	other threads:[~2026-01-07 17:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260107170415.80275-1-scott.k.mitch1@gmail.com>
2026-01-07 17:01 ` |SUCCESS| " qemudev
2026-01-07 17:05 ` checkpatch [this message]
2026-01-07 17:06 ` qemudev
2026-01-07 18:07 ` |FAILURE| " 0-day Robot
2026-01-08  6:09 ` |SUCCESS| pw159636 [PATCH] [v3] net: optimize raw checksum computati dpdklab
2026-01-08  6:24 ` dpdklab
2026-01-08  6:38 ` dpdklab
2026-01-08  8:18 ` dpdklab
2026-01-08  8:44 ` dpdklab
2026-01-08 17:06 ` dpdklab
2026-01-08 20:50 ` dpdklab
2026-01-08 21:05 ` dpdklab
2026-01-08 21:12 ` dpdklab
2026-01-08 21:14 ` dpdklab
2026-01-08 21:19 ` dpdklab
2026-01-09  0:38 ` |PENDING| " dpdklab
2026-01-09  1:42 ` |FAILURE| " dpdklab
2026-01-09  1:45 ` dpdklab
2026-01-09  2:24 ` |WARNING| " dpdklab
2026-01-09  2:24 ` dpdklab
2026-01-09  2:37 ` dpdklab
2026-01-09  2:39 ` dpdklab
2026-01-09  2:45 ` dpdklab
2026-01-09  2:50 ` dpdklab
2026-01-09 17:48 ` 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=20260107170512.058FF123FA0@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).