automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw33462 [PATCH v7 03/14] net/avf: enable queue and device
Date: Wed, 10 Jan 2018 14:01:16 +0100 (CET)	[thread overview]
Message-ID: <20180110130116.380BD1B232@dpdk.org> (raw)
In-Reply-To: <1515589326-126210-4-git-send-email-wenzhuo.lu@intel.com>

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

_coding style issues_


CHECK:BRACES: Unbalanced braces around else statement
#180: FILE: drivers/net/avf/avf_ethdev.c:119:
+	} else

CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#1227: FILE: drivers/net/avf/avf_rxtx.h:117:
+	printf("Queue %d Rx_desc %d: QW0: 0x%016"PRIx64" QW1: 0x%016"PRIx64"
",

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1227: FILE: drivers/net/avf/avf_rxtx.h:117:
+	printf("Queue %d Rx_desc %d: QW0: 0x%016"PRIx64" QW1: 0x%016"PRIx64"
",

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1233: FILE: drivers/net/avf/avf_rxtx.h:123:
+	printf("Queue %d Rx_desc %d: QW0: 0x%016"PRIx64" QW1: 0x%016"PRIx64

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1234: FILE: drivers/net/avf/avf_rxtx.h:124:
+	       " QW2: 0x%016"PRIx64" QW3: 0x%016"PRIx64"
", rxq->queue_id,

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#1266: FILE: drivers/net/avf/avf_rxtx.h:156:
+	printf("Queue %d %s %d: QW0: 0x%016"PRIx64" QW1: 0x%016"PRIx64"
",

total: 0 errors, 0 warnings, 6 checks, 1577 lines checked

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

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1515589326-126210-4-git-send-email-wenzhuo.lu@intel.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=20180110130116.380BD1B232@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=wenzhuo.lu@intel.com \
    /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).