From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Howard Wang <howard_wang@realsil.com.cn>
Subject: |WARNING| pw148202 [PATCH v6 17/17] net/r8169: add driver_start and driver_stop
Date: Fri, 8 Nov 2024 13:18:29 +0100 (CET) [thread overview]
Message-ID: <20241108121829.793F3123161@dpdk.org> (raw)
In-Reply-To: <20241108121123.248797-18-howard_wang@realsil.com.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148202
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <HwSuppDashVer>
#219: FILE: drivers/net/r8169/r8169_dash.c:168:
+ switch (hw->HwSuppDashVer) {
CHECK:CAMELCASE: Avoid CamelCase: <AllowAccessDashOcp>
#258: FILE: drivers/net/r8169/r8169_dash.c:207:
+ if (!hw->AllowAccessDashOcp)
CHECK:MACRO_ARG_REUSE: Macro argument reuse '_M' - possible side-effects?
#288: FILE: drivers/net/r8169/r8169_dash.h:22:
+#define HW_DASH_SUPPORT_CMAC(_M) (HW_DASH_SUPPORT_TYPE_2(_M) || HW_DASH_SUPPORT_TYPE_3(_M))
total: 0 errors, 0 warnings, 3 checks, 246 lines checked
next prev parent reply other threads:[~2024-11-08 12:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108121123.248797-18-howard_wang@realsil.com.cn>
2024-11-08 11:44 ` |SUCCESS| pw148186-148202 " qemudev
2024-11-08 11:48 ` qemudev
2024-11-08 12:18 ` checkpatch [this message]
2024-11-08 13:38 ` |SUCCESS| pw148186-148202 [PATCH] [v6,17/17] net/r8169: add driver_s dpdklab
2024-11-08 13:38 ` dpdklab
2024-11-08 13:44 ` dpdklab
2024-11-08 13:45 ` |PENDING| " dpdklab
2024-11-08 13:46 ` |SUCCESS| " dpdklab
2024-11-08 13:48 ` |SUCCESS| pw148202 [PATCH v6 17/17] net/r8169: add driver_start and driver_stop 0-day Robot
2024-11-08 13:51 ` |SUCCESS| pw148186-148202 [PATCH] [v6,17/17] net/r8169: add driver_s dpdklab
2024-11-08 13:52 ` dpdklab
2024-11-08 14:05 ` dpdklab
2024-11-08 14:33 ` dpdklab
2024-11-08 14:36 ` dpdklab
2024-11-08 14:56 ` dpdklab
2024-11-08 15:05 ` dpdklab
2024-11-08 15:15 ` dpdklab
2024-11-08 15:20 ` dpdklab
2024-11-08 15:28 ` dpdklab
2024-11-08 15:56 ` 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=20241108121829.793F3123161@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).