automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Subject: |WARNING| pw106120 [PATCH] net/tap: Bug fix to populate fds in secondary process
Date: Thu, 20 Jan 2022 12:12:49 +0100 (CET)	[thread overview]
Message-ID: <20220120111249.9B97412091F@dpdk.org> (raw)
In-Reply-To: <20220120111215.76058-1-kumaraparamesh92@gmail.com>

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

_coding style issues_


WARNING:BRACES: braces {} are not necessary for single statement blocks
#149: FILE: drivers/net/tap/rte_eth_tap.c:922:
+	if (rte_eal_process_type() == RTE_PROC_PRIMARY) {
+		tap_mp_req_on_rxtx(dev);
+	}

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#393: FILE: lib/ethdev/rte_ethdev.h:4991:
+/**
+* Get rte_eth_dev from device name. The device name should be specified

WARNING:TYPO_SPELLING: 'sucessful' may be misspelled - perhaps 'successful'?
#402: FILE: lib/ethdev/rte_ethdev.h:5000:
+*   - rte_eth_dev if sucessful 

ERROR:TRAILING_WHITESPACE: trailing whitespace
#402: FILE: lib/ethdev/rte_ethdev.h:5000:
+*   - rte_eth_dev if sucessful $

total: 1 errors, 3 warnings, 302 lines checked
ERROR: symbol rte_get_eth_dev_by_name is added in the DPDK_22 section, but is expected to be added in the EXPERIMENTAL section of the version map

       reply	other threads:[~2022-01-20 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220120111215.76058-1-kumaraparamesh92@gmail.com>
2022-01-20 11:12 ` checkpatch [this message]
2022-01-20 12:39 ` |SUCCESS| " 0-day Robot

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=20220120111249.9B97412091F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=kumaraparamesh92@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).