From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harman Kalra <hkalra@marvell.com>
Subject: |WARNING| pw137396 [PATCH v4 23/23] net/cnxk: other flow operations
Date: Tue, 27 Feb 2024 20:21:49 +0100 (CET) [thread overview]
Message-ID: <20240227192149.8A5C4122320@dpdk.org> (raw)
In-Reply-To: <20240227191550.137687-24-hkalra@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/137396
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#119: FILE: drivers/net/cnxk/cnxk_rep_flow.c:294:
+ plt_rep_dbg("Flow Destroy: flow 0x%" PRIu64 ", portid %d", msg_fd_meta.flow,
total: 0 errors, 0 warnings, 1 checks, 470 lines checked
next prev parent reply other threads:[~2024-02-27 19:21 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227191550.137687-24-hkalra@marvell.com>
2024-02-27 19:05 ` |SUCCESS| pw137374-137396 " qemudev
2024-02-27 19:09 ` qemudev
2024-02-27 19:21 ` checkpatch [this message]
2024-02-28 2:25 ` |SUCCESS| pw137374-137396 [PATCH] [v4,23/23] net/cnxk: other flow op dpdklab
2024-02-28 2:28 ` dpdklab
2024-02-28 2:29 ` dpdklab
2024-02-28 2:33 ` dpdklab
2024-02-28 2:41 ` dpdklab
2024-02-28 2:41 ` dpdklab
2024-02-28 2:42 ` dpdklab
2024-02-28 2:43 ` dpdklab
2024-02-28 2:44 ` dpdklab
2024-02-28 2:45 ` dpdklab
2024-02-28 2:46 ` dpdklab
2024-02-28 2:56 ` dpdklab
2024-02-28 2:58 ` dpdklab
2024-02-28 2:59 ` dpdklab
2024-02-28 3:41 ` dpdklab
2024-02-28 3:49 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:08 ` dpdklab
2024-02-28 4:08 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:10 ` dpdklab
2024-02-28 4:10 ` dpdklab
2024-02-28 4:13 ` dpdklab
2024-02-28 4:19 ` dpdklab
2024-02-28 4:20 ` dpdklab
2024-02-28 4:20 ` dpdklab
2024-02-28 4:22 ` dpdklab
2024-02-28 4:22 ` dpdklab
2024-02-28 4:23 ` dpdklab
2024-02-28 4:26 ` dpdklab
2024-02-28 4:28 ` dpdklab
2024-02-28 4:30 ` dpdklab
2024-02-28 5:11 ` dpdklab
2024-02-28 5:11 ` dpdklab
2024-02-28 6:20 ` dpdklab
2024-02-28 6:30 ` dpdklab
2024-02-28 6:45 ` dpdklab
2024-02-28 6:45 ` dpdklab
2024-02-28 6:46 ` dpdklab
2024-02-28 6:46 ` dpdklab
2024-02-28 6:48 ` dpdklab
2024-02-28 6:54 ` dpdklab
2024-02-28 7:00 ` dpdklab
2024-02-28 7:01 ` dpdklab
2024-02-28 7:03 ` dpdklab
2024-02-28 7:09 ` dpdklab
2024-02-28 7:20 ` dpdklab
2024-02-28 7:22 ` dpdklab
2024-02-28 10:58 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 22:12 ` dpdklab
2024-02-29 16:42 ` dpdklab
2024-02-29 16:44 ` dpdklab
2024-02-29 16:47 ` dpdklab
2024-02-29 17:02 ` dpdklab
2024-02-29 17:32 ` dpdklab
2024-02-29 19:21 ` dpdklab
2024-02-29 19:52 ` 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=20240227192149.8A5C4122320@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hkalra@marvell.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).