automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-test-report] |WARNING| pw72577 [PATCH] net/kni: set packet input port in eth_kni_rx()
Date: Wed,  1 Jul 2020 09:50:46 +0200 (CEST)	[thread overview]
Message-ID: <20200701075046.40B211C197@dpdk.org> (raw)
In-Reply-To: <20200701074941.3847658-1-ferruh.yigit@intel.com>

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

_coding style issues_


WARNING:BRACES: braces {} are not necessary for single statement blocks
#92: FILE: drivers/net/kni/rte_eth_kni.c:85:
+	for (i = 0; i < nb_pkts; i++) {
+		bufs[i]->port = kni_q->internals->port_id;
+	}

ERROR:TRAILING_WHITESPACE: trailing whitespace
#95: FILE: drivers/net/kni/rte_eth_kni.c:88:
+^I$

WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'jiancheng pei <jpei@sonicwall.com>'

total: 1 errors, 2 warnings, 0 checks, 28 lines checked

       reply	other threads:[~2020-07-01  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200701074941.3847658-1-ferruh.yigit@intel.com>
2020-07-01  7:50 ` checkpatch [this message]
2020-07-01 10:15 ` [dpdk-test-report] |SUCCESS| pw72577 " 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=20200701075046.40B211C197@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=ferruh.yigit@intel.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).