From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tianhao Zhang <zhang.tianhao2@zte.com.cn>
Subject: |WARNING| pw159243 [PATCH v1] net/zxdh: add pcie bar channel check
Date: Tue, 9 Dec 2025 03:35:28 +0100 (CET) [thread overview]
Message-ID: <20251209023528.1CD7E125284@dpdk.org> (raw)
In-Reply-To: <20251209021609.3911854-1-zhang.tianhao2@zte.com.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159243
_coding style issues_
ERROR:OPEN_BRACE: that open brace { should be on the previous line
#85: FILE: drivers/net/zxdh/zxdh_np.c:3702:
+ if((*p_item_num & ZXDH_DTB_SPACE_LEFT_MASK) == ZXDH_DTB_SPACE_LEFT_MASK)
+ {
ERROR:SPACING: space required before the open parenthesis '('
#85: FILE: drivers/net/zxdh/zxdh_np.c:3702:
+ if((*p_item_num & ZXDH_DTB_SPACE_LEFT_MASK) == ZXDH_DTB_SPACE_LEFT_MASK)
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#86: FILE: drivers/net/zxdh/zxdh_np.c:3703:
+ {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#88: FILE: drivers/net/zxdh/zxdh_np.c:3705:
+ return ZXDH_RC_DTB_BAR_ABNORMAL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#88: FILE: drivers/net/zxdh/zxdh_np.c:3705:
+ return ZXDH_RC_DTB_BAR_ABNORMAL;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#89: FILE: drivers/net/zxdh/zxdh_np.c:3706:
+ }$
ERROR:TRAILING_WHITESPACE: trailing whitespace
#90: FILE: drivers/net/zxdh/zxdh_np.c:3707:
+^I$
total: 4 errors, 3 warnings, 0 checks, 27 lines checked
next prev parent reply other threads:[~2025-12-09 2:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251209021609.3911854-1-zhang.tianhao2@zte.com.cn>
2025-12-09 2:01 ` |SUCCESS| " qemudev
2025-12-09 2:06 ` qemudev
2025-12-09 2:35 ` checkpatch [this message]
2025-12-09 3:22 ` 0-day Robot
2025-12-09 3:22 ` 0-day Robot
2025-12-09 9:20 ` |PENDING| pw159243 [PATCH] [v1] " dpdklab
2025-12-09 9:23 ` |SUCCESS| " dpdklab
2025-12-09 9:24 ` |PENDING| " dpdklab
2025-12-09 9:28 ` |SUCCESS| " dpdklab
2025-12-09 9:28 ` |PENDING| " dpdklab
2025-12-09 9:31 ` dpdklab
2025-12-09 9:43 ` |SUCCESS| " dpdklab
2025-12-09 9:45 ` |FAILURE| " dpdklab
2025-12-09 9:45 ` |SUCCESS| " dpdklab
2025-12-09 9:46 ` dpdklab
2025-12-09 9:49 ` dpdklab
2025-12-09 9:53 ` dpdklab
2025-12-09 9:56 ` dpdklab
2025-12-09 9:59 ` dpdklab
2025-12-09 10:03 ` dpdklab
2025-12-09 10:05 ` dpdklab
2025-12-09 10:54 ` dpdklab
2025-12-09 12:39 ` dpdklab
2025-12-10 6:25 ` dpdklab
2025-12-10 6:42 ` 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=20251209023528.1CD7E125284@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=zhang.tianhao2@zte.com.cn \
/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).