automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jie Liu <liujie5@linkdatatechnology.com>
Subject: |WARNING| pw155045 [PATCH v3 14/14] net/sxe: add Solve compilation problems.
Date: Mon,  7 Jul 2025 14:03:18 +0200 (CEST)	[thread overview]
Message-ID: <20250707120318.610C7125304@dpdk.org> (raw)
In-Reply-To: <20250707115819.12826-14-liujie5@linkdatatechnology.com>

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

_coding style issues_


CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around adapter->link_thread_running
#487: FILE: drivers/net/sxe/pf/sxe_phy.c:60:
+	rte_atomic_store_explicit(&(adapter->link_thread_running), 0, rte_memory_order_seq_cst);

CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around adapter->link_thread_running
#496: FILE: drivers/net/sxe/pf/sxe_phy.c:71:
+	while (rte_atomic_load_explicit(&(adapter->link_thread_running),

CHECK:BRACES: Blank lines aren't necessary after an open brace '{'
#498: FILE: drivers/net/sxe/pf/sxe_phy.c:73:
+		rte_memory_order_seq_cst)) {
+

CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around adapter->link_thread_running
#507: FILE: drivers/net/sxe/pf/sxe_phy.c:154:
+		if (!rte_atomic_exchange_explicit(&(adapter->link_thread_running), 1,

total: 0 errors, 0 warnings, 4 checks, 628 lines checked

  parent reply	other threads:[~2025-07-07 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250707115819.12826-14-liujie5@linkdatatechnology.com>
2025-07-07 11:28 ` |FAILURE| pw155032-155045 " qemudev
2025-07-07 12:03 ` checkpatch [this message]
2025-07-07 12:23 ` |FAILURE| pw155032-155045 [PATCH] [v3, " dpdklab
2025-07-07 12:43 ` |FAILURE| pw155045 [PATCH v3 " 0-day Robot

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=20250707120318.610C7125304@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=liujie5@linkdatatechnology.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).