From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harman Kalra <hkalra@marvell.com>
Subject: |WARNING| pw137793 [PATCH v5 23/23] net/cnxk: other flow operations
Date: Fri, 1 Mar 2024 20:20:48 +0100 (CET) [thread overview]
Message-ID: <20240301192048.44F6D122335@dpdk.org> (raw)
In-Reply-To: <20240301191451.57168-24-hkalra@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/137793
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRIu64>
#132: 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, 477 lines checked
next parent reply other threads:[~2024-03-01 19:20 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301191451.57168-24-hkalra@marvell.com>
2024-03-01 19:20 ` checkpatch [this message]
2024-03-01 22:54 ` |SUCCESS| pw137771-137793 [PATCH] [v5,23/23] net/cnxk: other flow op dpdklab
2024-03-01 23:15 ` dpdklab
2024-03-01 23:21 ` dpdklab
2024-03-01 23:24 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:27 ` dpdklab
2024-03-01 23:29 ` dpdklab
2024-03-01 23:29 ` dpdklab
2024-03-01 23:35 ` dpdklab
2024-03-01 23:36 ` dpdklab
2024-03-01 23:37 ` dpdklab
2024-03-01 23:38 ` dpdklab
2024-03-01 23:39 ` dpdklab
2024-03-01 23:39 ` dpdklab
2024-03-01 23:41 ` dpdklab
2024-03-01 23:52 ` dpdklab
2024-03-02 0:12 ` dpdklab
2024-03-02 0:14 ` dpdklab
2024-03-02 0:37 ` dpdklab
2024-03-02 0:45 ` dpdklab
2024-03-02 2:17 ` dpdklab
2024-03-02 2:19 ` dpdklab
2024-03-02 2:26 ` dpdklab
2024-03-02 2:27 ` dpdklab
2024-03-02 2:28 ` dpdklab
2024-03-02 2:36 ` dpdklab
2024-03-02 2:37 ` dpdklab
2024-03-02 2:38 ` dpdklab
2024-03-02 2:39 ` dpdklab
2024-03-02 2:39 ` dpdklab
2024-03-02 2:40 ` dpdklab
2024-03-02 2:40 ` dpdklab
2024-03-02 2:41 ` dpdklab
2024-03-02 2:41 ` dpdklab
2024-03-02 2:42 ` dpdklab
2024-03-02 2:42 ` dpdklab
2024-03-02 2:43 ` dpdklab
2024-03-02 2:43 ` dpdklab
2024-03-02 2:43 ` dpdklab
2024-03-02 2:43 ` dpdklab
2024-03-02 2:43 ` dpdklab
2024-03-02 2:44 ` dpdklab
2024-03-02 2:45 ` dpdklab
2024-03-02 2:50 ` dpdklab
2024-03-02 2:51 ` dpdklab
2024-03-02 2:51 ` dpdklab
2024-03-02 2:51 ` dpdklab
2024-03-02 2:52 ` dpdklab
2024-03-02 2:53 ` dpdklab
2024-03-02 2:55 ` dpdklab
2024-03-02 2:57 ` dpdklab
2024-03-02 2:58 ` dpdklab
2024-03-02 3:00 ` dpdklab
2024-03-02 3:07 ` dpdklab
2024-03-02 3:10 ` dpdklab
2024-03-02 3:10 ` dpdklab
2024-03-02 3:38 ` dpdklab
2024-03-02 3:39 ` dpdklab
2024-03-02 3:40 ` dpdklab
2024-03-02 3:40 ` dpdklab
2024-03-02 3:41 ` dpdklab
2024-03-02 3:42 ` dpdklab
2024-03-02 3:42 ` dpdklab
2024-03-02 3:54 ` dpdklab
2024-03-02 3:56 ` dpdklab
2024-03-02 4:56 ` dpdklab
2024-03-02 5:12 ` dpdklab
2024-03-02 5:35 ` dpdklab
2024-03-03 3:21 ` dpdklab
2024-03-06 6:35 ` dpdklab
2024-03-06 7:45 ` dpdklab
2024-03-06 8:02 ` 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=20240301192048.44F6D122335@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).