From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Frank Du <frank.du@intel.com>
Subject: |WARNING| pw140285 [PATCH v3] net/af_xdp: fix umem map size for zero copy
Date: Thu, 23 May 2024 09:12:37 +0200 (CEST) [thread overview]
Message-ID: <20240523071237.F2A3E12367B@dpdk.org> (raw)
In-Reply-To: <20240523065302.2345392-1-frank.du@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/140285
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <PRId64>
#121: FILE: drivers/net/af_xdp/rte_eth_af_xdp.c:1065:
+ "next: %p, cur: %p(len: %" PRId64 " )
",
total: 0 errors, 0 warnings, 1 checks, 65 lines checked
next prev parent reply other threads:[~2024-05-23 7:12 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240523065302.2345392-1-frank.du@intel.com>
2024-05-23 6:44 ` |SUCCESS| " qemudev
2024-05-23 6:49 ` qemudev
2024-05-23 7:12 ` checkpatch [this message]
2024-05-23 8:04 ` 0-day Robot
2024-05-23 10:42 ` |SUCCESS| pw140285 [PATCH] [v3] net/af_xdp: fix umem map size for ze dpdklab
2024-05-23 10:44 ` dpdklab
2024-05-23 10:46 ` dpdklab
2024-05-23 10:46 ` dpdklab
2024-05-23 10:46 ` dpdklab
2024-05-23 10:47 ` dpdklab
2024-05-23 10:48 ` dpdklab
2024-05-23 10:49 ` dpdklab
2024-05-23 10:49 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 11:05 ` dpdklab
2024-05-23 11:05 ` dpdklab
2024-05-23 11:06 ` dpdklab
2024-05-23 11:06 ` dpdklab
2024-05-23 11:06 ` dpdklab
2024-05-23 11:07 ` dpdklab
2024-05-23 11:07 ` dpdklab
2024-05-23 11:08 ` dpdklab
2024-05-23 11:10 ` dpdklab
2024-05-23 11:10 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:19 ` dpdklab
2024-05-23 11:29 ` dpdklab
2024-05-23 11:30 ` dpdklab
2024-05-23 11:33 ` dpdklab
2024-05-23 11:34 ` dpdklab
2024-05-23 11:36 ` dpdklab
2024-05-23 11:41 ` dpdklab
2024-05-23 11:44 ` dpdklab
2024-05-23 11:44 ` dpdklab
2024-05-23 11:45 ` dpdklab
2024-05-23 11:48 ` dpdklab
2024-05-23 11:55 ` dpdklab
2024-05-23 12:07 ` dpdklab
2024-05-23 12:07 ` dpdklab
2024-05-23 12:08 ` dpdklab
2024-05-23 12:08 ` dpdklab
2024-05-23 12:09 ` dpdklab
2024-05-23 12:10 ` dpdklab
2024-05-23 12:10 ` dpdklab
2024-05-23 12:11 ` dpdklab
2024-05-23 12:12 ` dpdklab
2024-05-23 12:20 ` dpdklab
2024-05-23 12:20 ` dpdklab
2024-05-23 12:21 ` dpdklab
2024-05-23 12:21 ` dpdklab
2024-05-23 12:22 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:25 ` dpdklab
2024-05-23 12:27 ` dpdklab
2024-05-23 12:27 ` dpdklab
2024-05-23 12:27 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:31 ` dpdklab
2024-05-23 12:31 ` dpdklab
2024-05-23 12:31 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:33 ` dpdklab
2024-05-23 12:35 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:47 ` dpdklab
2024-05-23 12:53 ` dpdklab
2024-05-23 12:54 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:56 ` dpdklab
2024-05-23 12:58 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:27 ` dpdklab
2024-05-23 13:45 ` dpdklab
2024-05-23 13:54 ` 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=20240523071237.F2A3E12367B@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).