automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw149507 [PATCH v3 3/3] drivers/net: add diagnostics macros to make code portable
Date: Sat, 28 Dec 2024 04:20:11 +0100 (CET)	[thread overview]
Message-ID: <20241228032011.41C75126FB8@dpdk.org> (raw)
In-Reply-To: <1735355910-1175-4-git-send-email-andremue@linux.microsoft.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/149507

_coding style issues_


WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#224: FILE: drivers/net/fm10k/fm10k_rxtx_vec.c:473:
+__rte_diagnostic_pop

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#375: FILE: drivers/net/i40e/i40e_rxtx_vec_altivec.c:290:
+__rte_diagnostic_pop

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#655: FILE: drivers/net/i40e/i40e_rxtx_vec_sse.c:473:
+__rte_diagnostic_pop

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#987: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:586:
+__rte_diagnostic_pop

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#1022: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:878:
+__rte_diagnostic_pop

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (24, 0)
#1141: FILE: drivers/net/ice/ice_rxtx_vec_avx2.c:443:
 			if (rxq->vsi->adapter->pf.dev_data->dev_conf.rxmode.offloads &
[...]
+__rte_diagnostic_push

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (24, 0)
#1213: FILE: drivers/net/ice/ice_rxtx_vec_avx512.c:473:
 			if (rxq->vsi->adapter->pf.dev_data->dev_conf.rxmode.offloads &
[...]
+__rte_diagnostic_push

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#1312: FILE: drivers/net/ice/ice_rxtx_vec_sse.c:433:
+__rte_diagnostic_pop

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (16, 0)
#1332: FILE: drivers/net/ice/ice_rxtx_vec_sse.c:497:
 		if (rxq->vsi->adapter->pf.dev_data->dev_conf.rxmode.offloads &
[...]
+__rte_diagnostic_push

WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#1446: FILE: drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c:474:
+__rte_diagnostic_pop

ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#1556: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.h:133:
+__rte_diagnostic_pop
 	for (pos = 0; pos < mcqe_n; ) {

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (24, 0)
#1580: FILE: drivers/net/mlx5/mlx5_rxtx_vec_sse.h:359:
 			if (!(pos & 0x7) && pos < mcqe_n) {
+__rte_diagnostic_push

total: 1 errors, 11 warnings, 0 checks, 1296 lines checked

  parent reply	other threads:[~2024-12-28  3:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1735355910-1175-4-git-send-email-andremue@linux.microsoft.com>
2024-12-28  2:47 ` |SUCCESS| pw149505-149507 " qemudev
2024-12-28  2:51 ` qemudev
2024-12-28  3:20 ` checkpatch [this message]
2024-12-28  3:48 ` |PENDING| pw149505-149507 [PATCH] [v3,3/3] drivers/net: add diagnost dpdklab
2024-12-28  3:48 ` |FAILURE| " dpdklab
2024-12-28  3:54 ` |SUCCESS| " dpdklab
2024-12-28  4:00 ` |PENDING| " dpdklab
2024-12-28  4:01 ` |SUCCESS| " dpdklab
2024-12-28  4:02 ` |PENDING| " dpdklab
2024-12-28  4:04 ` |FAILURE| pw149507 [PATCH v3 3/3] drivers/net: add diagnostics macros to make code portable 0-day Robot
2024-12-28  4:09 ` |SUCCESS| pw149505-149507 [PATCH] [v3,3/3] drivers/net: add diagnost dpdklab
2024-12-28  4:13 ` dpdklab
2024-12-28  4:14 ` dpdklab
2024-12-28  4:14 ` |PENDING| " dpdklab
2024-12-28  4:17 ` |SUCCESS| " dpdklab
2024-12-28  4:19 ` |FAILURE| " dpdklab
2024-12-28  4:19 ` |SUCCESS| " dpdklab
2024-12-28  4:21 ` |FAILURE| " dpdklab
2024-12-28  4:22 ` |SUCCESS| " dpdklab
2024-12-28  4:23 ` dpdklab
2024-12-28  4:25 ` |WARNING| " dpdklab
2024-12-28  4:30 ` |SUCCESS| " dpdklab
2024-12-28  4:48 ` dpdklab
2024-12-28  4:59 ` |WARNING| " dpdklab
2024-12-28  5:54 ` dpdklab
2024-12-28  6:11 ` |FAILURE| " 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=20241228032011.41C75126FB8@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=andremue@linux.microsoft.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).