automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <skori@marvell.com>
Subject: |WARNING| pw131773 [PATCH v5 10/12] app/graph: add graph command line interfaces
Date: Thu, 21 Sep 2023 12:11:09 +0200 (CEST)	[thread overview]
Message-ID: <20230921101109.BA78B120802@dpdk.org> (raw)
In-Reply-To: <20230921100832.2036256-11-skori@marvell.com>

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

_coding style issues_


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

ERROR:SPACING: space required before the open parenthesis '('
#402: FILE: app/graph/graph.c:278:
+		if(rte_lcore_is_enabled(lcore_id))

WARNING:BRACES: braces {} are not necessary for any arm of this statement
#409: FILE: app/graph/graph.c:285:
+			if (eal_coremask & core_num) {
[...]
+			} else {
[...]

total: 1 errors, 2 warnings, 678 lines checked

           reply	other threads:[~2023-09-21 10:11 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230921100832.2036256-11-skori@marvell.com>]

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=20230921101109.BA78B120802@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=skori@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).