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| pw144427 [PATCH] net/r8169: add support for phy configuration
Date: Wed, 25 Sep 2024 09:38:13 +0200 (CEST)	[thread overview]
Message-ID: <20240925073814.049CD121D9E@dpdk.org> (raw)
In-Reply-To: <20240925073737.37607-1-howard_wang@realsil.com.cn>

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

_coding style issues_


CHECK:CAMELCASE: Avoid CamelCase: <HwSuppCheckPhyDisableModeVer>
#117: FILE: drivers/net/r8169/r8169_ethdev.h:42:
+	u8  HwSuppCheckPhyDisableModeVer;

CHECK:CAMELCASE: Avoid CamelCase: <HwSuppMaxPhyLinkSpeed>
#122: FILE: drivers/net/r8169/r8169_ethdev.h:47:
+	u32 HwSuppMaxPhyLinkSpeed;

CHECK:CAMELCASE: Avoid CamelCase: <PhyState>
#176: FILE: drivers/net/r8169/r8169_phy.c:374:
+rtl_wait_phy_ups_resume(struct rtl_hw *hw, u16 PhyState)

ERROR:CODE_INDENT: code indent should use tabs where possible
#275: FILE: drivers/net/r8169/r8169_phy.c:473:
+^I                MII_ADVERTISE) & ~(ADVERTISE_10HALF | ADVERTISE_10FULL | ADVERTISE_100HALF |$

ERROR:CODE_INDENT: code indent should use tabs where possible
#276: FILE: drivers/net/r8169/r8169_phy.c:474:
+^I                                   ADVERTISE_100FULL));$

ERROR:CODE_INDENT: code indent should use tabs where possible
#278: FILE: drivers/net/r8169/r8169_phy.c:476:
+^I                MII_CTRL1000) & ~(ADVERTISE_1000HALF | ADVERTISE_1000FULL));$

ERROR:CODE_INDENT: code indent should use tabs where possible
#280: FILE: drivers/net/r8169/r8169_phy.c:478:
+^I                              0xA5D4) & ~(RTK_ADVERTISE_2500FULL | RTK_ADVERTISE_5000FULL));$

WARNING:LONG_LINE: line length of 101 exceeds 100 columns
#302: FILE: drivers/net/r8169/r8169_phy.c:500:
+			PMD_INIT_LOG(NOTICE, "PHY watch dog not clear, value = 0x%x", phy_reg_value);

ERROR:CODE_INDENT: code indent should use tabs where possible
#309: FILE: drivers/net/r8169/r8169_phy.c:507:
+^I^I                                  (BIT_10 | BIT_9 | BIT_8));$

CHECK:BRACES: braces {} should be used on all arms of this statement
#337: FILE: drivers/net/r8169/r8169_phy.c:535:
+	if (hw->hw_ram_code_ver == hw->sw_ram_code_ver) {
[...]
+	} else
[...]

CHECK:CAMELCASE: Avoid CamelCase: <HwHasWrRamCodeToMicroP>
#339: FILE: drivers/net/r8169/r8169_phy.c:537:
+		hw->HwHasWrRamCodeToMicroP = TRUE;

CHECK:BRACES: Unbalanced braces around else statement
#340: FILE: drivers/net/r8169/r8169_phy.c:538:
+	} else

CHECK:CAMELCASE: Avoid CamelCase: <NotWrRamCodeToMicroP>
#386: FILE: drivers/net/r8169/r8169_phy.c:584:
+	if (hw->NotWrRamCodeToMicroP == TRUE)

CHECK:BOOL_COMPARISON: Using comparison to TRUE is error prone
#386: FILE: drivers/net/r8169/r8169_phy.c:584:
+	if (hw->NotWrRamCodeToMicroP == TRUE)

CHECK:USLEEP_RANGE: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
#423: FILE: drivers/net/r8169/r8169_phy.c:621:
+			udelay(100);

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#594: FILE: drivers/net/r8169/r8169_phy.h:23:
+#define MII_LPA ^I^I0x05^I/* Link partner ability reg    */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#604: FILE: drivers/net/r8169/r8169_phy.h:33:
+#define MII_RERRCOUNTER ^I0x15^I/* Receive error counter       */$

WARNING:TYPO_SPELLING: 'asymetric' may be misspelled - perhaps 'asymmetric'?
#657: FILE: drivers/net/r8169/r8169_phy.h:86:
+#define ADVERTISE_PAUSE_ASYM	0x0800	/* Try for asymetric pause     */

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#660: FILE: drivers/net/r8169/r8169_phy.h:89:
+#define ADVERTISE_LPACK ^I0x4000^I/* Ack link partners response  */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#661: FILE: drivers/net/r8169/r8169_phy.h:90:
+#define ADVERTISE_NPAGE ^I0x8000^I/* Next page bit               */$

WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#669: FILE: drivers/net/r8169/r8169_phy.h:98:
+#define RTK_ADVERTISE_10000FULL ^I0x1000$

total: 5 errors, 7 warnings, 9 checks, 600 lines checked

  parent reply	other threads:[~2024-09-25  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240925073737.37607-1-howard_wang@realsil.com.cn>
2024-09-25  7:10 ` qemudev
2024-09-25  7:38 ` checkpatch [this message]
2024-09-25 15:20 ` 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=20240925073814.049CD121D9E@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).