automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Oleksandr Kolomeiets <okl-plv@napatech.com>
Subject: |WARNING| pw153209 [PATCH v1 08/25] net/ntnic: improve logging format specifiers
Date: Wed, 30 Apr 2025 15:52:56 +0200 (CEST)	[thread overview]
Message-ID: <20250430135256.8660A123FA7@dpdk.org> (raw)
In-Reply-To: <20250430134840.402553-9-okl-plv@napatech.com>

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

_coding style issues_


CHECK:CAMELCASE: Avoid CamelCase: <PRIu32>
#215: FILE: drivers/net/ntnic/link_mgmt/link_agx_100g/nt4ga_agx_link_100g.c:370:
+		NT_LOG(DBG, NTNIC, "Port %i: Faults(Local = %" PRIu32 ", Remote = %" PRIu32 ")",

CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#521: FILE: drivers/net/ntnic/nthw/flow_api/profile_inline/flow_api_hw_db_inline.c:582:
+			fprintf(file, "    QW0 dyn %" PRIu64 ", ofs %" PRIu64

CHECK:CAMELCASE: Avoid CamelCase: <PRIu16>
#608: FILE: drivers/net/ntnic/nthw/flow_api/profile_inline/flow_api_profile_inline.c:1163:
+					"%" PRIu16 ",hw id %i",

CHECK:CAMELCASE: Avoid CamelCase: <PRIx32>
#662: FILE: drivers/net/ntnic/nthw/model/nthw_fpga_model.c:908:
+				PRIu16 ": (%08i ,%08" PRIu32 ") (0x%08" PRIx32 ",%08"

WARNING:TYPO_SPELLING: 'alloced' may be misspelled - perhaps 'allocated'?
#795: FILE: drivers/net/ntnic/ntnic_ethdev.c:979:
+	NT_LOG_DBGX(DBG, NTNIC, "num_queues_alloced=%i, New queues=%i, Max queues=%d",

total: 0 errors, 1 warnings, 4 checks, 608 lines checked

           reply	other threads:[~2025-04-30 13:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250430134840.402553-9-okl-plv@napatech.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=20250430135256.8660A123FA7@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=okl-plv@napatech.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).