automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jun Wang <junwang01@cestc.cn>
Subject: |WARNING| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture packet coredump
Date: Tue, 19 Mar 2024 17:18:43 +0100 (CET)	[thread overview]
Message-ID: <20240319161843.156D01223F7@dpdk.org> (raw)
In-Reply-To: <1710865092-2796-1-git-send-email-junwang01@cestc.cn>

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

_coding style issues_


WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one

ERROR:CODE_INDENT: code indent should use tabs where possible
#96: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4329:
+^I    ^I!ad->sdp3_no_tx_disable) {$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#96: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4329:
+^I    ^I!ad->sdp3_no_tx_disable) {$

WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#126: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4339:
+				if (!__atomic_test_and_set(&ad->link_thread_running, __ATOMIC_SEQ_CST)) {

ERROR:CODE_INDENT: code indent should use tabs where possible
#128: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4341:
+^I^I^I^I ^I* the IXGBE_FLAG_NEED_LINK_CONFIG flag only$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#128: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4341:
+^I^I^I^I ^I* the IXGBE_FLAG_NEED_LINK_CONFIG flag only$

WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#128: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4341:
+					/* To avoid race condition between threads, set
+				 	* the IXGBE_FLAG_NEED_LINK_CONFIG flag only

ERROR:CODE_INDENT: code indent should use tabs where possible
#129: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4342:
+^I^I^I^I ^I* when there is no link thread running.$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#129: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4342:
+^I^I^I^I ^I* when there is no link thread running.$

ERROR:CODE_INDENT: code indent should use tabs where possible
#130: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4343:
+^I^I^I^I ^I*/$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#130: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4343:
+^I^I^I^I ^I*/$

WARNING:LONG_LINE: line length of 104 exceeds 100 columns
#134: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4347:
+							ixgbe_dev_setup_link_thread_handler, dev) < 0) {

WARNING:LONG_LINE_COMMENT: line length of 102 exceeds 100 columns
#137: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4350:
+						/* NOTE: review for potential ordering optimization */

WARNING:LONG_LINE: line length of 107 exceeds 100 columns
#138: FILE: drivers/net/ixgbe/ixgbe_ethdev.c:4351:
+						__atomic_clear(&ad->link_thread_running, __ATOMIC_SEQ_CST);

total: 4 errors, 10 warnings, 0 checks, 86 lines checked

  parent reply	other threads:[~2024-03-19 16:18 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1710865092-2796-1-git-send-email-junwang01@cestc.cn>
2024-03-19 16:00 ` |SUCCESS| " qemudev
2024-03-19 16:05 ` qemudev
2024-03-19 16:18 ` checkpatch [this message]
2024-03-19 16:55 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac dpdklab
2024-03-19 16:55 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:01 ` dpdklab
2024-03-19 17:02 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:06 ` dpdklab
2024-03-19 17:06 ` dpdklab
2024-03-19 17:07 ` dpdklab
2024-03-19 17:13 ` dpdklab
2024-03-19 17:13 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:16 ` dpdklab
2024-03-19 17:23 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture packet coredump 0-day Robot
2024-03-19 17:25 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac dpdklab
2024-03-19 17:26 ` dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:30 ` |FAILURE| " dpdklab
2024-03-19 17:31 ` dpdklab
2024-03-19 17:31 ` |SUCCESS| " dpdklab
2024-03-19 17:32 ` |FAILURE| " dpdklab
2024-03-19 17:36 ` dpdklab
2024-03-19 17:41 ` |SUCCESS| " dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 17:52 ` dpdklab
2024-03-19 18:05 ` dpdklab
2024-03-19 18:06 ` |FAILURE| " dpdklab
2024-03-19 18:08 ` |SUCCESS| " dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:48 ` dpdklab
2024-03-21  5:40 ` dpdklab
2024-03-21  6:05 ` 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=20240319161843.156D01223F7@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=junwang01@cestc.cn \
    --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).