[dpdk-test-report] |WARNING| pw62487 [PATCH] Working Towards Making DPDK Compile with Additional Warning Flags

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: devyn.johnson@banduracyber.com
Subject: [dpdk-test-report] |WARNING| pw62487 [PATCH] Working Towards Making DPDK Compile with Additional Warning Flags
Date: Tue,  5 Nov 2019 19:17:08 +0100 (CET)	[thread overview]
Message-ID: <20191105181708.60FF71BF53@dpdk.org> (raw)
In-Reply-To: <20191105181640.3714-1-Devyn.Johnson@BanduraCyber.com>

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

_coding style issues_


ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#126: FILE: lib/librte_cryptodev/rte_cryptodev.c:806:
+							(void*)dev, nb_qpairs);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#352: FILE: lib/librte_eal/common/eal_common_tailqs.c:68:
+			i, tailq->name, (void*)head->tqh_first, (void*)head->tqh_last);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#352: FILE: lib/librte_eal/common/eal_common_tailqs.c:68:
+			i, tailq->name, (void*)head->tqh_first, (void*)head->tqh_last);

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#411: FILE: lib/librte_eal/common/include/rte_bitmap.h:98:
+	uint32_t * __restrict array1_byte_offset, uint32_t * __restrict array1_slabs,

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#411: FILE: lib/librte_eal/common/include/rte_bitmap.h:98:
+	uint32_t * __restrict array1_byte_offset, uint32_t * __restrict array1_slabs,

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#412: FILE: lib/librte_eal/common/include/rte_bitmap.h:99:
+	uint32_t * __restrict array2_byte_offset, uint32_t * __restrict array2_slabs)

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#412: FILE: lib/librte_eal/common/include/rte_bitmap.h:99:
+	uint32_t * __restrict array2_byte_offset, uint32_t * __restrict array2_slabs)

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#514: FILE: lib/librte_eal/common/include/rte_hexdump.h:53:
+rte_memdump(FILE *f, const char * title, const void * buf, const unsigned int len);

ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#514: FILE: lib/librte_eal/common/include/rte_hexdump.h:53:
+rte_memdump(FILE *f, const char * title, const void * buf, const unsigned int len);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#616: FILE: lib/librte_eal/common/malloc_elem.c:669:
+	fprintf(f, "Malloc element at %p (%s)
", (const void*)elem,

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#620: FILE: lib/librte_eal/common/malloc_elem.c:672:
+	fprintf(f, "  prev: %p next: %p
", (void*)elem->prev, (void*)elem->next);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#620: FILE: lib/librte_eal/common/malloc_elem.c:672:
+	fprintf(f, "  prev: %p next: %p
", (void*)elem->prev, (void*)elem->next);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#631: FILE: lib/librte_eal/linux/eal/eal.c:454:
+				"' option
", rte_mem_cfg_addr, (void*)mem_config);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#680: FILE: lib/librte_mbuf/rte_mbuf.c:477:
+	       (const void*)m, (uint64_t)m->buf_iova, (unsigned)m->buf_len);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#680: FILE: lib/librte_mbuf/rte_mbuf.c:477:
+	       (const void*)m, (uint64_t)m->buf_iova, (unsigned)m->buf_len);

WARNING:LONG_LINE: line over 90 characters
#689: FILE: lib/librte_mbuf/rte_mbuf.c:487:
+			(const void*)m, (void*)rte_pktmbuf_mtod(m, void *), (unsigned)m->data_len);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#689: FILE: lib/librte_mbuf/rte_mbuf.c:487:
+			(const void*)m, (void*)rte_pktmbuf_mtod(m, void *), (unsigned)m->data_len);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#689: FILE: lib/librte_mbuf/rte_mbuf.c:487:
+			(const void*)m, (void*)rte_pktmbuf_mtod(m, void *), (unsigned)m->data_len);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#689: FILE: lib/librte_mbuf/rte_mbuf.c:487:
+			(const void*)m, (void*)rte_pktmbuf_mtod(m, void *), (unsigned)m->data_len);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#724: FILE: lib/librte_mempool/rte_mempool.c:1203:
+	fprintf(f, "mempool <%s>@%p
", mp->name, (void*)mp);

ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#737: FILE: lib/librte_ring/rte_ring.c:235:
+	fprintf(f, "ring <%s>@%p
", r->name, (const void*)r);

total: 18 errors, 3 warnings, 550 lines checked

next      parent reply	other threads:[~2019-11-05 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191105181640.3714-1-Devyn.Johnson@BanduraCyber.com>
2019-11-05 18:17 ` checkpatch [this message]
2019-11-06 12:09 ` [dpdk-test-report] |WARNING| pw62487 " 0-day Robot

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=20191105181708.60FF71BF53@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=devyn.johnson@banduracyber.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).