automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Somnath Kotur <somnath.kotur@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw74314 [PATCH 14/14] net/bnxt: add debug logs to the TF-ULP layer
Date: Fri, 17 Jul 2020 11:57:14 +0200 (CEST)	[thread overview]
Message-ID: <20200717095714.90AAF1BFB9@dpdk.org> (raw)
In-Reply-To: <20200717094935.9337-15-somnath.kotur@broadcom.com>

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

_coding style issues_


CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#1118: FILE: drivers/net/bnxt/tf_ulp/ulp_template_debug.c:579:
+	BNXT_TF_DBG(DEBUG, "FlowHdl=0x%016" PRIx64 " FlowID=0x%016" PRIx64 "
",

ERROR:C99_COMMENTS: do not use C99 // comments
#1579: FILE: drivers/net/bnxt/tf_ulp/ulp_tf_debug.c:26:
+#if 0 // def TF_EEM_DEBUG

WARNING:IF_0: Consider removing the code enclosed by this #if 0 and its #endif
#1579: FILE: drivers/net/bnxt/tf_ulp/ulp_tf_debug.c:26:
+#if 0 // def TF_EEM_DEBUG

ERROR:C99_COMMENTS: do not use C99 // comments
#1626: FILE: drivers/net/bnxt/tf_ulp/ulp_tf_debug.c:73:
+#if 0 //def TF_EEM_DUMP

WARNING:IF_0: Consider removing the code enclosed by this #if 0 and its #endif
#1626: FILE: drivers/net/bnxt/tf_ulp/ulp_tf_debug.c:73:
+#if 0 //def TF_EEM_DUMP

WARNING:IF_0: Consider removing the code enclosed by this #if 0 and its #endif
#2545: FILE: drivers/net/bnxt/tf_ulp/ulp_tf_debug.c:992:
+#if 0

ERROR:C99_COMMENTS: do not use C99 // comments
#2655: FILE: drivers/net/bnxt/tf_ulp/ulp_tf_debug.c:1102:
+	//tf_dump_tables(&bp->tfp, tbl_scope_id);

total: 3 errors, 3 warnings, 1 checks, 2578 lines checked

           reply	other threads:[~2020-07-17  9:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200717094935.9337-15-somnath.kotur@broadcom.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=20200717095714.90AAF1BFB9@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=somnath.kotur@broadcom.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).