From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ariel Otilibili <ariel.otilibili@6wind.com>
Subject: |WARNING| pw150592 [PATCH v3 2/2] net/af_xdp: Refactor af_xdp_tx_zc
Date: Wed, 29 Jan 2025 00:12:49 +0100 (CET) [thread overview]
Message-ID: <20250128231249.B9637126FF4@dpdk.org> (raw)
In-Reply-To: <20250128231152.249497-3-ariel.otilibili@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150592
_coding style issues_
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#146: FILE: drivers/net/af_xdp/rte_eth_af_xdp.c:570:
+static struct rte_mbuf *
+maybe_create_mbuf(struct pkt_tx_queue *txq, uint32_t *idx_tx,
+ struct xsk_umem_info *umem) {
ERROR:SPACING: space required before the open parenthesis '('
#171: FILE: drivers/net/af_xdp/rte_eth_af_xdp.c:595:
+ if(is_mbuf_equal)
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 18)
#240: FILE: drivers/net/af_xdp/rte_eth_af_xdp.c:635:
+ if (!local_mbuf)
+ goto out;
WARNING:TABSTOP: Statements should start on a tabstop
#241: FILE: drivers/net/af_xdp/rte_eth_af_xdp.c:636:
+ goto out;
total: 2 errors, 2 warnings, 0 checks, 158 lines checked
next prev parent reply other threads:[~2025-01-28 23:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250128231152.249497-3-ariel.otilibili@6wind.com>
2025-01-28 22:39 ` |SUCCESS| pw150591-150592 [PATCH v3 2/2] net/af_xdp: Refactor af_xdp_tx_zc() qemudev
2025-01-28 22:43 ` qemudev
2025-01-28 23:12 ` checkpatch [this message]
2025-01-29 0:03 ` |SUCCESS| pw150592 " 0-day Robot
2025-01-29 10:33 ` |SUCCESS| pw150591-150592 [PATCH] [v3,2/2] net/af_xdp: Refactor af_x dpdklab
2025-01-29 10:33 ` dpdklab
2025-01-29 10:33 ` dpdklab
2025-01-29 10:40 ` dpdklab
2025-01-29 10:46 ` dpdklab
2025-01-29 10:50 ` dpdklab
2025-01-29 10:54 ` |PENDING| " dpdklab
2025-01-29 11:26 ` |SUCCESS| " dpdklab
2025-01-29 11:27 ` dpdklab
2025-01-29 11:28 ` dpdklab
2025-01-29 11:32 ` dpdklab
2025-01-29 11:33 ` |PENDING| " dpdklab
2025-01-29 11:34 ` |SUCCESS| " dpdklab
2025-01-29 11:40 ` dpdklab
2025-01-29 11:41 ` dpdklab
2025-01-29 11:42 ` |PENDING| " dpdklab
2025-01-29 11:47 ` |SUCCESS| " dpdklab
2025-01-29 12:06 ` |PENDING| " dpdklab
2025-01-29 12:14 ` |SUCCESS| " dpdklab
2025-01-29 12:27 ` dpdklab
2025-01-29 12:35 ` |PENDING| " dpdklab
2025-01-29 12:41 ` dpdklab
2025-01-29 12:47 ` |SUCCESS| " dpdklab
2025-01-29 13:25 ` |PENDING| " dpdklab
2025-01-29 13:33 ` |SUCCESS| " dpdklab
2025-01-29 13:41 ` dpdklab
2025-01-29 13:49 ` |WARNING| " dpdklab
2025-01-29 13:52 ` |SUCCESS| " dpdklab
2025-01-29 14:02 ` |WARNING| " dpdklab
2025-01-29 14:22 ` dpdklab
2025-01-29 15:07 ` |SUCCESS| " dpdklab
2025-01-29 15:58 ` dpdklab
2025-01-29 16:48 ` dpdklab
2025-01-29 18:26 ` dpdklab
2025-01-29 19:09 ` dpdklab
2025-01-30 2:28 ` dpdklab
2025-01-30 2:30 ` 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=20250128231249.B9637126FF4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ariel.otilibili@6wind.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).