automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shani Peretz <shperetz@nvidia.com>
Subject: |WARNING| pw143817 [PATCH] examples/flow_filtering: introduce use cases snippets
Date: Mon,  9 Sep 2024 15:54:14 +0200 (CEST)	[thread overview]
Message-ID: <20240909135414.61F0D121D10@dpdk.org> (raw)
In-Reply-To: <20240909135308.241258-1-shperetz@nvidia.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#1181: FILE: examples/flow_filtering/snippets/snippet_match_ipv4.c:5:
+#include <stdio.h>

total: 0 errors, 1 warnings, 1222 lines checked

  parent reply	other threads:[~2024-09-09 13:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240909135308.241258-1-shperetz@nvidia.com>
2024-09-09 13:33 ` |SUCCESS| " qemudev
2024-09-09 13:38 ` qemudev
2024-09-09 13:54 ` checkpatch [this message]
2024-09-09 14:45 ` |FAILURE| " 0-day Robot
2024-09-09 15:06 ` |PENDING| pw143817 [PATCH] examples/flow_filtering: introduce use ca dpdklab
2024-09-09 15:12 ` |SUCCESS| " dpdklab
2024-09-09 15:13 ` dpdklab
2024-09-09 15:14 ` dpdklab
2024-09-09 15:16 ` dpdklab
2024-09-09 15:23 ` |PENDING| " dpdklab
2024-09-09 15:28 ` |SUCCESS| " dpdklab
2024-09-09 15:28 ` |PENDING| " dpdklab
2024-09-09 15:42 ` |SUCCESS| " dpdklab
2024-09-09 15:45 ` |PENDING| " dpdklab
2024-09-09 17:05 ` |SUCCESS| " dpdklab
2024-09-09 17:17 ` dpdklab
2024-09-09 17:30 ` dpdklab
2024-09-09 18:07 ` dpdklab
2024-09-09 18:08 ` dpdklab
2024-09-09 18:12 ` dpdklab
2024-09-09 18:20 ` dpdklab
2024-09-09 18:32 ` dpdklab
2024-09-09 19:00 ` dpdklab
2024-09-09 19:10 ` dpdklab
2024-09-09 19:46 ` dpdklab
2024-09-16 11:08 ` dpdklab
2024-09-16 19:29 ` 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=20240909135414.61F0D121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=shperetz@nvidia.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).