automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Matteo Croce <mcroce@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw32287 [PATCH v2] i40e: remove warning
Date: Thu, 14 Dec 2017 21:41:24 +0100 (CET)	[thread overview]
Message-ID: <20171214204124.9F4124BE1@dpdk.org> (raw)
In-Reply-To: <20171214204040.28134-1-mcroce@redhat.com>

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

_coding style issues_


CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#47: FILE: drivers/net/i40e/base/i40e_common.c:3934:
+				   "HW Capability: wr_csr_prot = 0x"PRIX64"

",

CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#69: FILE: drivers/net/i40e/base/i40e_nvm.c:123:
+			   "NVM acquire type %d failed time_left="PRIu64" ret=%d aq_err=%d
",

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#69: FILE: drivers/net/i40e/base/i40e_nvm.c:123:
+			   "NVM acquire type %d failed time_left="PRIu64" ret=%d aq_err=%d
",

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#78: FILE: drivers/net/i40e/base/i40e_nvm.c:145:
+				   "NVM acquire timed out, wait "PRIu64" ms before trying again. status=%d aq_err=%d
",

CHECK:CAMELCASE: Avoid CamelCase: <PRId64>
#87: FILE: drivers/net/i40e/base/i40e_nvm.c:1237:
+				   "NVMUPD: write semaphore expired (%d >= "PRId64"), retrying
",

CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#87: FILE: drivers/net/i40e/base/i40e_nvm.c:1237:
+				   "NVMUPD: write semaphore expired (%d >= "PRId64"), retrying
",

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

           reply	other threads:[~2017-12-14 20:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171214204040.28134-1-mcroce@redhat.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=20171214204124.9F4124BE1@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=mcroce@redhat.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).