From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Frank Du <frank.du@intel.com>
Subject: |WARNING| pw140023 [PATCH v2] net/af_xdp: fix umem map size for zero copy
Date: Sat, 11 May 2024 07:43:46 +0200 (CEST) [thread overview]
Message-ID: <20240511054346.B217F121E57@dpdk.org> (raw)
In-Reply-To: <20240511052618.1890677-1-frank.du@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140023
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRId64>
#107: FILE: drivers/net/af_xdp/rte_eth_af_xdp.c:1060:
+ "next: %p, cur: %p(len: %" PRId64 " )
",
total: 0 errors, 0 warnings, 1 checks, 60 lines checked
next prev parent reply other threads:[~2024-05-11 5:43 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240511052618.1890677-1-frank.du@intel.com>
2024-05-11 5:21 ` |SUCCESS| " qemudev
2024-05-11 5:26 ` qemudev
2024-05-11 5:43 ` checkpatch [this message]
2024-05-11 6:38 ` |SUCCESS| pw140023 [PATCH] [v2] net/af_xdp: fix umem map size for ze dpdklab
2024-05-11 6:40 ` dpdklab
2024-05-11 6:41 ` dpdklab
2024-05-11 6:42 ` dpdklab
2024-05-11 6:42 ` dpdklab
2024-05-11 6:42 ` dpdklab
2024-05-11 6:43 ` dpdklab
2024-05-11 6:43 ` dpdklab
2024-05-11 6:44 ` dpdklab
2024-05-11 6:44 ` |SUCCESS| pw140023 [PATCH v2] net/af_xdp: fix umem map size for zero copy 0-day Robot
2024-05-11 6:44 ` |SUCCESS| pw140023 [PATCH] [v2] net/af_xdp: fix umem map size for ze dpdklab
2024-05-11 6:45 ` dpdklab
2024-05-11 6:45 ` dpdklab
2024-05-11 6:45 ` dpdklab
2024-05-11 6:46 ` dpdklab
2024-05-11 6:46 ` dpdklab
2024-05-11 6:46 ` dpdklab
2024-05-11 6:47 ` dpdklab
2024-05-11 6:47 ` dpdklab
2024-05-11 6:49 ` dpdklab
2024-05-11 6:49 ` dpdklab
2024-05-11 6:49 ` dpdklab
2024-05-11 6:50 ` dpdklab
2024-05-11 6:50 ` dpdklab
2024-05-11 6:51 ` dpdklab
2024-05-11 6:51 ` dpdklab
2024-05-11 6:51 ` dpdklab
2024-05-11 6:52 ` dpdklab
2024-05-11 6:52 ` dpdklab
2024-05-11 6:52 ` dpdklab
2024-05-11 6:53 ` dpdklab
2024-05-11 6:53 ` dpdklab
2024-05-11 6:53 ` dpdklab
2024-05-11 6:53 ` dpdklab
2024-05-11 6:54 ` dpdklab
2024-05-11 6:54 ` dpdklab
2024-05-11 6:55 ` dpdklab
2024-05-11 6:55 ` dpdklab
2024-05-11 6:55 ` dpdklab
2024-05-11 6:55 ` dpdklab
2024-05-11 6:56 ` dpdklab
2024-05-11 6:57 ` dpdklab
2024-05-11 6:57 ` dpdklab
2024-05-11 6:57 ` dpdklab
2024-05-11 6:58 ` dpdklab
2024-05-11 6:58 ` dpdklab
2024-05-11 6:58 ` dpdklab
2024-05-11 7:00 ` dpdklab
2024-05-11 7:01 ` dpdklab
2024-05-11 7:01 ` dpdklab
2024-05-11 7:02 ` dpdklab
2024-05-11 7:04 ` dpdklab
2024-05-11 7:05 ` dpdklab
2024-05-11 7:05 ` dpdklab
2024-05-11 7:07 ` dpdklab
2024-05-11 7:08 ` dpdklab
2024-05-11 7:08 ` dpdklab
2024-05-11 7:08 ` dpdklab
2024-05-11 7:08 ` dpdklab
2024-05-11 7:09 ` dpdklab
2024-05-11 7:10 ` dpdklab
2024-05-11 7:12 ` dpdklab
2024-05-11 7:14 ` dpdklab
2024-05-11 7:15 ` dpdklab
2024-05-11 7:20 ` dpdklab
2024-05-11 7:21 ` dpdklab
2024-05-11 7:23 ` dpdklab
2024-05-11 7:25 ` dpdklab
2024-05-11 7:29 ` |FAILURE| " dpdklab
2024-05-11 7:29 ` |SUCCESS| " dpdklab
2024-05-11 7:30 ` |FAILURE| " dpdklab
2024-05-11 7:30 ` |SUCCESS| " dpdklab
2024-05-11 7:32 ` |FAILURE| " dpdklab
2024-05-11 7:33 ` |SUCCESS| " dpdklab
2024-05-11 7:35 ` dpdklab
2024-05-11 7:35 ` |FAILURE| " dpdklab
2024-05-11 7:37 ` |SUCCESS| " dpdklab
2024-05-11 7:38 ` |FAILURE| " dpdklab
2024-05-11 7:39 ` dpdklab
2024-05-11 7:40 ` dpdklab
2024-05-11 7:42 ` dpdklab
2024-05-11 7:43 ` dpdklab
2024-05-11 7:44 ` |SUCCESS| " dpdklab
2024-05-11 7:48 ` |FAILURE| " dpdklab
2024-05-11 7:50 ` dpdklab
2024-05-11 7:56 ` |SUCCESS| " dpdklab
2024-05-11 8:06 ` dpdklab
2024-05-11 8:57 ` dpdklab
2024-05-11 9:29 ` dpdklab
2024-05-11 9:34 ` 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=20240511054346.B217F121E57@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=frank.du@intel.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).