automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw143994 [PATCH v2 14/14] drivers: use per line logging in helpers
Date: Thu, 12 Sep 2024 10:31:47 +0200 (CEST)	[thread overview]
Message-ID: <20240912083147.F1D11121D10@dpdk.org> (raw)
In-Reply-To: <20240912082643.1532679-15-david.marchand@redhat.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#765: FILE: drivers/common/cnxk/roc_platform.h:279:
+#define RTE_LOGTYPE_tim cnxk_logtype_tim

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#765: FILE: drivers/common/cnxk/roc_platform.h:279:
+#define RTE_LOGTYPE_tim cnxk_logtype_tim

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'sc' - possible side-effects?
#2177: FILE: drivers/net/bnx2x/bnx2x_logs.h:21:
+#define PMD_DRV_LOG(level, sc, ...) \
+	RTE_LOG_LINE_PREFIX(level, BNX2X_DRIVER, "[%s:%d(%s)] ", \
+		__func__ RTE_LOG_COMMA __LINE__ RTE_LOG_COMMA \
+		(sc)->devinfo.name ? (sc)->devinfo.name : "", __VA_ARGS__)

ERROR:SPACING: space required before the open parenthesis '('
#2190: FILE: drivers/net/bnx2x/bnx2x_logs.h:30:
+#define PMD_RX_LOG(...) do { } while(0)

ERROR:SPACING: space required before the open parenthesis '('
#2201: FILE: drivers/net/bnx2x/bnx2x_logs.h:37:
+#define PMD_TX_LOG(...) do { } while(0)

CHECK:MACRO_ARG_REUSE: Macro argument reuse 'sc' - possible side-effects?
#2209: FILE: drivers/net/bnx2x/bnx2x_logs.h:41:
+#define PMD_DEBUG_PERIODIC_LOG(level, sc, ...) \
+	RTE_LOG_LINE_PREFIX(level, BNX2X_DRIVER, "%s(%s): ", \
+		__func__ RTE_LOG_COMMA (sc)->devinfo.name ? (sc)->devinfo.name : "", __VA_ARGS__)

WARNING:SPACING: space prohibited between function name and open parenthesis '('
#2211: FILE: drivers/net/bnx2x/bnx2x_logs.h:43:
+		__func__ RTE_LOG_COMMA (sc)->devinfo.name ? (sc)->devinfo.name : "", __VA_ARGS__)

CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#2434: FILE: drivers/net/dpaa2/dpaa2_rxtx.c:402:
+		"fd_off=%d fd =%" PRIx64 ", meta = %d  bpid =%d, len=%d",

CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#3774: FILE: drivers/net/octeon_ep/otx_ep_rxtx.c:921:
+				    "last_pkt_count %" PRIu64 "new_pkts %d.",

ERROR:SPACING: space required before the open parenthesis '('
#4085: FILE: drivers/net/virtio/virtio_logs.h:21:
+#define PMD_RX_LOG(...) do { } while(0)

ERROR:SPACING: space required before the open parenthesis '('
#4095: FILE: drivers/net/virtio/virtio_logs.h:28:
+#define PMD_TX_LOG(...) do { } while(0)

ERROR:SPACING: space required before the open parenthesis '('
#4130: FILE: drivers/net/vmxnet3/vmxnet3_logs.h:18:
+#define PMD_RX_LOG(...) do { } while(0)

ERROR:SPACING: space required before the open parenthesis '('
#4140: FILE: drivers/net/vmxnet3/vmxnet3_logs.h:25:
+#define PMD_TX_LOG(...) do { } while(0)

ERROR:SPACING: space required before the open parenthesis '('
#4150: FILE: drivers/net/vmxnet3/vmxnet3_logs.h:32:
+#define PMD_TX_FREE_LOG(...) do { } while(0)

total: 7 errors, 3 warnings, 3347 lines checked

  parent reply	other threads:[~2024-09-12  8:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240912082643.1532679-15-david.marchand@redhat.com>
2024-09-12  8:04 ` |SUCCESS| pw143982-143994 " qemudev
2024-09-12  8:09 ` qemudev
2024-09-12  8:31 ` checkpatch [this message]
2024-09-12  9:24 ` |SUCCESS| pw143994 " 0-day Robot
2024-09-12 10:51 ` |SUCCESS| pw143982-143994 [PATCH] [v2,14/14] drivers: use per line l dpdklab
2024-09-12 11:03 ` dpdklab
2024-09-12 11:09 ` dpdklab
2024-09-12 11:39 ` dpdklab
2024-09-12 16:04 ` |PENDING| " dpdklab
2024-09-12 16:33 ` dpdklab
2024-09-12 17:01 ` dpdklab
2024-09-12 17:44 ` |SUCCESS| " dpdklab
2024-09-12 17:53 ` dpdklab
2024-09-12 17:55 ` dpdklab
2024-09-12 18:34 ` dpdklab
2024-09-12 18:38 ` dpdklab
2024-09-12 18:43 ` dpdklab
2024-09-12 19:03 ` |FAILURE| " dpdklab
2024-09-12 20:03 ` |SUCCESS| " dpdklab
2024-09-12 20:33 ` dpdklab
2024-09-12 21:17 ` |FAILURE| " dpdklab
2024-09-12 23:42 ` |SUCCESS| " dpdklab
2024-09-15  7:12 ` dpdklab
2024-09-15 11:53 ` |FAILURE| " dpdklab
2024-09-16 15:42 ` |SUCCESS| " dpdklab
2024-09-16 15:58 ` dpdklab
2024-09-16 15:59 ` |FAILURE| " dpdklab
2024-09-16 16:01 ` dpdklab
2024-09-16 16:08 ` |SUCCESS| " dpdklab
2024-09-16 16:13 ` dpdklab
2024-09-16 16:20 ` dpdklab
2024-09-16 16:32 ` dpdklab
2024-09-17 14:57 ` dpdklab
2024-09-17 23:41 ` dpdklab
2024-09-18  7:41 ` dpdklab
2024-09-21 14:29 ` dpdklab
2024-09-21 14:41 ` dpdklab

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=20240912083147.F1D11121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=david.marchand@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).