automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Howard Wang <howard_wang@realsil.com.cn>
Subject: |WARNING| pw158211 [PATCH v2 3/3] net/r8169: fix issues reported by Coverity
Date: Wed, 29 Oct 2025 03:09:04 +0100 (CET)	[thread overview]
Message-ID: <20251029020904.9EC9D1261CB@dpdk.org> (raw)
In-Reply-To: <20251029020838.401035-4-howard_wang@realsil.com.cn>

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

_coding style issues_


CHECK:CAMELCASE: Avoid CamelCase: <EnableTxNoClose>
#179: FILE: drivers/net/r8169/r8169_rxtx.c:1808:
+	enable_tx_no_close = hw->EnableTxNoClose;

total: 0 errors, 0 warnings, 1 checks, 113 lines checked

  parent reply	other threads:[~2025-10-29  2:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251029020838.401035-4-howard_wang@realsil.com.cn>
2025-10-29  1:38 ` |SUCCESS| pw158209-158211 " qemudev
2025-10-29  1:42 ` qemudev
2025-10-29  2:09 ` checkpatch [this message]
2025-10-29  2:31 ` |PENDING| pw158209-158211 [PATCH] [v2,3/3] net/r8169: fix issues rep dpdklab
2025-10-29  2:33 ` dpdklab
2025-10-29  2:33 ` |SUCCESS| " dpdklab
2025-10-29  2:38 ` dpdklab
2025-10-29  2:42 ` |PENDING| " dpdklab
2025-10-29  2:45 ` |WARNING| " dpdklab
2025-10-29  2:46 ` |FAILURE| " dpdklab
2025-10-29  2:47 ` |PENDING| " dpdklab
2025-10-29  2:50 ` |SUCCESS| " dpdklab
2025-10-29  2:53 ` dpdklab
2025-10-29  2:55 ` dpdklab
2025-10-29  2:56 ` |PENDING| " dpdklab
2025-10-29  2:56 ` |SUCCESS| " dpdklab
2025-10-29  3:10 ` dpdklab
2025-10-29  3:14 ` dpdklab
2025-10-29  3:15 ` |WARNING| " dpdklab
2025-10-29  3:16 ` dpdklab
2025-10-29  4:22 ` |SUCCESS| pw158211 [PATCH v2 3/3] net/r8169: fix issues reported by Coverity 0-day Robot
2025-10-29  4:22 ` 0-day Robot
2025-10-29  5:08 ` |SUCCESS| pw158209-158211 [PATCH] [v2,3/3] net/r8169: fix issues rep dpdklab
2025-10-29  5:21 ` dpdklab
2025-10-29  6:58 ` dpdklab
2025-10-29 19:59 ` 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=20251029020904.9EC9D1261CB@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=howard_wang@realsil.com.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).