From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bing Zhao <bingz@nvidia.com>
Subject: |WARNING| pw154646 [PATCH 2/2] net/mlx5: use consecutive memory for all Tx queues
Date: Mon, 23 Jun 2025 19:36:42 +0200 (CEST) [thread overview]
Message-ID: <20250623173642.D3CF51252D0@dpdk.org> (raw)
In-Reply-To: <20250623173524.128125-3-bingz@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154646
_coding style issues_
WARNING:BRACES: braces {} are not necessary for single statement blocks
#403: FILE: drivers/net/mlx5/mlx5_devx.c:1518:
+ if (!ret) {
+ priv->acc_tx_wq_mem.cur_off += act_size;
+ }
total: 0 errors, 1 warnings, 0 checks, 393 lines checked
next prev parent reply other threads:[~2025-06-23 17:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250623173524.128125-3-bingz@nvidia.com>
2025-06-23 17:01 ` |SUCCESS| pw154645-154646 " qemudev
2025-06-23 17:05 ` qemudev
2025-06-23 17:36 ` checkpatch [this message]
2025-06-23 18:13 ` |SUCCESS| pw154645-154646 [PATCH] [2/2] net/mlx5: use consecutive me dpdklab
2025-06-23 18:15 ` dpdklab
2025-06-23 18:20 ` |PENDING| " dpdklab
2025-06-23 18:24 ` |FAILURE| " dpdklab
2025-06-23 18:26 ` dpdklab
2025-06-23 18:27 ` dpdklab
2025-06-23 18:28 ` |SUCCESS| pw154646 [PATCH 2/2] net/mlx5: use consecutive memory for all Tx queues 0-day Robot
2025-06-23 18:29 ` |FAILURE| pw154645-154646 [PATCH] [2/2] net/mlx5: use consecutive me dpdklab
2025-06-23 18:31 ` dpdklab
2025-06-23 18:52 ` |PENDING| " dpdklab
2025-06-23 18:54 ` |SUCCESS| " dpdklab
2025-06-23 19:21 ` |FAILURE| " dpdklab
2025-06-23 20:25 ` |SUCCESS| " dpdklab
2025-06-23 20:27 ` |FAILURE| " dpdklab
2025-06-23 20:28 ` |SUCCESS| " dpdklab
2025-06-23 20:29 ` |FAILURE| " dpdklab
2025-06-23 21:06 ` |SUCCESS| " dpdklab
2025-06-24 1:12 ` 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=20250623173642.D3CF51252D0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bingz@nvidia.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).