automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tom Barbette <barbette@kth.se>
Subject: [dpdk-test-report] |WARNING| pw47476 mlx5: Support for rte_eth_rx_queue_count
Date: Fri, 26 Oct 2018 15:44:12 +0200 (CEST)	[thread overview]
Message-ID: <20181026134412.83D2C4CC7@dpdk.org> (raw)
In-Reply-To: <1540561347-88328-1-git-send-email-barbette@kth.se>

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

_coding style issues_


ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#64: FILE: drivers/net/mlx5/mlx5_rxtx.c:428:
+static uint32_t
+rx_queue_count(struct mlx5_rxq_data* rxq) {

ERROR:POINTER_LOCATION: "foo* bar" should be "foo *bar"
#65: FILE: drivers/net/mlx5/mlx5_rxtx.c:429:
+rx_queue_count(struct mlx5_rxq_data* rxq) {

CHECK:BRACES: Blank lines aren't necessary after an open brace '{'
#66: FILE: drivers/net/mlx5/mlx5_rxtx.c:430:
+rx_queue_count(struct mlx5_rxq_data* rxq) {
+

CHECK:BRACES: Blank lines aren't necessary before a close brace '}'
#75: FILE: drivers/net/mlx5/mlx5_rxtx.c:462:
+
+}

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#93: FILE: drivers/net/mlx5/mlx5_rxtx.c:480:
+    uint32_t used = rx_queue_count(rxq);$

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#121: FILE: drivers/net/mlx5/mlx5_rxtx.c:508:
+    return rx_queue_count(rxq);$

total: 2 errors, 2 warnings, 2 checks, 98 lines checked

           reply	other threads:[~2018-10-26 13:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1540561347-88328-1-git-send-email-barbette@kth.se>]

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=20181026134412.83D2C4CC7@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=barbette@kth.se \
    --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).