automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrew Rybchenko <arybchenko@solarflare.com>
Subject: [dpdk-test-report] |WARNING| pw26688 [PATCH 2/2] examples: adjust Rx and Tx descriptors to device limits
Date: Mon, 10 Jul 2017 17:08:22 +0200 (CEST)	[thread overview]
Message-ID: <20170710150822.163FC5A6A@dpdk.org> (raw)
In-Reply-To: <591819ba-f8aa-8afd-9f69-f40befb93016@solarflare.com>

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

_coding style issues_


WARNING:LEADING_SPACE: please, no spaces at the start of a line
#61: FILE: examples/bond/main.c:180:
+       uint16_t nb_rxd = RTE_RX_DESC_DEFAULT;$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#62: FILE: examples/bond/main.c:181:
+       uint16_t nb_txd = RTE_TX_DESC_DEFAULT;$

ERROR:CORRUPTED_PATCH: patch seems to be corrupt (line wrapped?)
#68: FILE: examples/bond/main.c:188:
(res=%d)
",

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#71: FILE: examples/bond/main.c:191:
+       retval = rte_eth_dev_adjust_nb_rx_tx_desc(portid, &nb_rxd, &nb_txd);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#72: FILE: examples/bond/main.c:192:
+       if (retval != 0)$

ERROR:TRAILING_WHITESPACE: trailing whitespace
#73: FILE: examples/bond/main.c:193:
+               rte_exit(EXIT_FAILURE, "port %u: $

ERROR:CODE_INDENT: code indent should use tabs where possible
#73: FILE: examples/bond/main.c:193:
+               rte_exit(EXIT_FAILURE, "port %u: $

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#73: FILE: examples/bond/main.c:193:
+               rte_exit(EXIT_FAILURE, "port %u: $

ERROR:SPACING: need consistent spacing around '%' (ctx:WxV)
#73: FILE: examples/bond/main.c:193:
+               rte_exit(EXIT_FAILURE, "port %u: 
                                             ^

ERROR:SPACING: spaces required around that ':' (ctx:VxW)
#73: FILE: examples/bond/main.c:193:
+               rte_exit(EXIT_FAILURE, "port %u: 
                                               ^

ERROR:CODE_INDENT: code indent should use tabs where possible
#75: FILE: examples/bond/main.c:194:
+                               "failed (res=%d)
", portid, retval);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#75: FILE: examples/bond/main.c:194:
+                               "failed (res=%d)
", portid, retval);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#79: FILE: examples/bond/main.c:197:
+       retval = rte_eth_rx_queue_setup(portid, 0, nb_rxd,$

ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)

total: 7 errors, 7 warnings, 22 lines checked

           reply	other threads:[~2017-07-10 15:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <591819ba-f8aa-8afd-9f69-f40befb93016@solarflare.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=20170710150822.163FC5A6A@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=arybchenko@solarflare.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).