From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw149503 [PATCH v2 3/3] drivers/net: add diagnostics macros to make code portable
Date: Sat, 28 Dec 2024 01:47:44 +0100 (CET) [thread overview]
Message-ID: <20241228004744.58ADE126FB8@dpdk.org> (raw)
In-Reply-To: <1735346757-14891-4-git-send-email-andremue@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/149503
_coding style issues_
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#223: FILE: drivers/net/fm10k/fm10k_rxtx_vec.c:473:
+__rte_diagnostic_pop
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#553: FILE: drivers/net/i40e/i40e_rxtx_vec_sse.c:473:
+__rte_diagnostic_pop
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#885: FILE: drivers/net/iavf/iavf_rxtx_vec_sse.c:586:
+__rte_diagnostic_pop
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#920: 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)
#1039: 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)
#1111: 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
#1210: 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)
#1230: 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
#1344: FILE: drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c:474:
+__rte_diagnostic_pop
total: 0 errors, 9 warnings, 0 checks, 1118 lines checked
next prev parent reply other threads:[~2024-12-28 0:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1735346757-14891-4-git-send-email-andremue@linux.microsoft.com>
2024-12-28 0:15 ` |SUCCESS| pw149501-149503 " qemudev
2024-12-28 0:20 ` qemudev
2024-12-28 0:47 ` checkpatch [this message]
2024-12-28 1:24 ` |FAILURE| pw149503 " 0-day Robot
2024-12-28 1:28 ` |FAILURE| pw149501-149503 [PATCH] [v2,3/3] drivers/net: add diagnost dpdklab
2024-12-28 1:31 ` |SUCCESS| " dpdklab
2024-12-28 1:38 ` dpdklab
2024-12-28 1:44 ` dpdklab
2024-12-28 1:46 ` dpdklab
2024-12-28 1:46 ` |FAILURE| " dpdklab
2024-12-28 1:49 ` |PENDING| " dpdklab
2024-12-28 1:52 ` |WARNING| " dpdklab
2024-12-28 1:52 ` |SUCCESS| " dpdklab
2024-12-28 1:53 ` dpdklab
2024-12-28 1:54 ` |WARNING| " dpdklab
2024-12-28 2:01 ` |FAILURE| " dpdklab
2024-12-28 2:02 ` dpdklab
2024-12-28 2:05 ` dpdklab
2024-12-28 2:09 ` |SUCCESS| " dpdklab
2024-12-28 2:18 ` |FAILURE| " dpdklab
2024-12-28 2:19 ` |WARNING| " dpdklab
2024-12-28 2:24 ` |FAILURE| " dpdklab
2024-12-28 2:30 ` |WARNING| " dpdklab
2024-12-28 2:39 ` dpdklab
2024-12-28 2:41 ` |FAILURE| " dpdklab
2024-12-28 2:43 ` dpdklab
2024-12-28 2:50 ` dpdklab
2024-12-28 2:51 ` dpdklab
2024-12-28 3:03 ` dpdklab
2024-12-28 3:15 ` dpdklab
2024-12-28 3:15 ` dpdklab
2024-12-28 3:21 ` 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=20241228004744.58ADE126FB8@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).