From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nithin Dabilpuram <nithind1988@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw67753 [PATCH v3 09/11] net/octeontx2: add tm debug support
Date: Fri, 3 Apr 2020 10:54:51 +0200 (CEST) [thread overview]
Message-ID: <20200403085451.A05731C1A1@dpdk.org> (raw)
In-Reply-To: <20200403085216.32684-10-nithind1988@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/67753
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#153: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:465:
+ nix_dump("
SQB Aura W0: Pool addr 0x%"PRIx64"",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#153: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:465:
+ nix_dump("
SQB Aura W0: Pool addr 0x%"PRIx64"",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#157: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:469:
+ nix_dump("SQB Aura W2: count %"PRIx64"",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#159: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:471:
+ nix_dump("SQB Aura W3: limit %"PRIx64"",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#163: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:475:
+ nix_dump("SQB Aura W4: fc_addr 0x%"PRIx64"
",
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#411: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:776:
+ nix_dump(" %s=0x%016"PRIx64,
CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#438: FILE: drivers/net/octeontx2/otx2_ethdev_debug.c:803:
+ nix_dump(" %s=0x%016"PRIx64,
total: 0 errors, 0 warnings, 7 checks, 382 lines checked
parent reply other threads:[~2020-04-03 8:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200403085216.32684-10-nithind1988@gmail.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=20200403085451.A05731C1A1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nithind1988@gmail.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).