From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yunjian Wang <wangyunjian@huawei.com>
Subject: |WARNING| pw159354 [PATCH 1/1] net/mlx5: fix memoy leak after device spawn failure
Date: Thu, 18 Dec 2025 10:30:27 +0100 (CET) [thread overview]
Message-ID: <20251218093027.3F39E1253FB@dpdk.org> (raw)
In-Reply-To: <1766050280-21036-1-git-send-email-wangyunjian@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159354
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#85: FILE: drivers/net/mlx5/linux/mlx5_os.c:1834:
+ for (i = 0; i < MLX5_FLOW_TYPE_MAXI; i++) {$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#85: FILE: drivers/net/mlx5/linux/mlx5_os.c:1834:
+ for (i = 0; i < MLX5_FLOW_TYPE_MAXI; i++) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#86: FILE: drivers/net/mlx5/linux/mlx5_os.c:1835:
+ if (!priv->flows[i])$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#86: FILE: drivers/net/mlx5/linux/mlx5_os.c:1835:
+ if (!priv->flows[i])$
ERROR:CODE_INDENT: code indent should use tabs where possible
#87: FILE: drivers/net/mlx5/linux/mlx5_os.c:1836:
+ continue;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#87: FILE: drivers/net/mlx5/linux/mlx5_os.c:1836:
+ continue;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#88: FILE: drivers/net/mlx5/linux/mlx5_os.c:1837:
+ mlx5_ipool_destroy(priv->flows[i]);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: drivers/net/mlx5/linux/mlx5_os.c:1837:
+ mlx5_ipool_destroy(priv->flows[i]);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#89: FILE: drivers/net/mlx5/linux/mlx5_os.c:1838:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#89: FILE: drivers/net/mlx5/linux/mlx5_os.c:1838:
+ }$
total: 5 errors, 5 warnings, 0 checks, 11 lines checked
next parent reply other threads:[~2025-12-18 9:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1766050280-21036-1-git-send-email-wangyunjian@huawei.com>
2025-12-18 9:30 ` checkpatch [this message]
2025-12-18 10:02 ` |SUCCESS| " qemudev
2025-12-18 10:07 ` qemudev
2025-12-18 10:49 ` 0-day Robot
2025-12-18 10:49 ` 0-day Robot
2025-12-18 11:31 ` |SUCCESS| pw159354 [PATCH] [1/1] net/mlx5: fix memoy leak after devi dpdklab
2025-12-18 11:36 ` dpdklab
2025-12-18 11:37 ` |PENDING| " dpdklab
2025-12-18 11:41 ` |SUCCESS| " dpdklab
2025-12-18 11:48 ` |PENDING| " dpdklab
2025-12-18 11:52 ` |SUCCESS| " dpdklab
2025-12-18 11:55 ` dpdklab
2025-12-18 11:55 ` dpdklab
2025-12-18 12:10 ` |PENDING| " dpdklab
2025-12-18 12:14 ` |SUCCESS| " dpdklab
2025-12-18 12:26 ` |PENDING| " dpdklab
2025-12-18 12:51 ` |SUCCESS| " dpdklab
2025-12-18 12:57 ` dpdklab
2025-12-18 12:59 ` dpdklab
2025-12-18 15:11 ` dpdklab
2025-12-18 15:53 ` dpdklab
2025-12-19 1:23 ` 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=20251218093027.3F39E1253FB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=wangyunjian@huawei.com \
/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).