automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-test-report] |WARNING| [PATCH 17/32] net/dpaa2: dpbp based mempool hw offload driver
Date: Sun,  4 Dec 2016 13:45:21 +0100 (CET)	[thread overview]
Message-ID: <20161204124521.93F14FA9F@dpdk.org> (raw)
In-Reply-To: <1480875447-23680-18-git-send-email-hemant.agrawal@nxp.com>

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

_coding style issues_


WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#445: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.c:263:
+		       void **obj_table, unsigned count)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#455: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.c:273:
+	unsigned n = 0;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#525: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.c:343:
+		  void * const *obj_table, unsigned n)

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#602: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:48:
+	void *addr; /*!< The address from where DPAA2 will carve out the
+			* buffers. 'addr' should be 'NULL' if user wants

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#604: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:50:
+			* asked DPAA2 to reserve during 'nadk init' */

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#606: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:52:
+				* of the memory provided in addr */

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#606: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:52:
+	phys_addr_t    phys_addr;  /*!< corresponding physical address
+				* of the memory provided in addr */

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#609: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:55:
+			* any headroom to be reserved and alignment */

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#612: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:58:
+			*in by DPAA2 for each buffer pool */

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#630: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:76:
+			* of each buffer pool */

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#630: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:76:
+	struct buf_pool_cfg buf_pool; /* Configuration
+			* of each buffer pool */

CHECK:MACRO_ARG_PRECEDENCE: Macro argument 'mp' may be better as '(mp)' to avoid precedence issues
#645: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:91:
+#define mempool_to_bpinfo(mp) ((struct dpaa2_bp_info *)mp->pool_data)

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#653: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpbp.h:99:
+		       void **obj_table, unsigned count);

total: 0 errors, 12 warnings, 1 checks, 537 lines checked

           reply	other threads:[~2016-12-04 12:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1480875447-23680-18-git-send-email-hemant.agrawal@nxp.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=20161204124521.93F14FA9F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=hemant.agrawal@nxp.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).