From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Howard Wang <howard_wang@realsil.com.cn>
Subject: |WARNING| pw145936 [PATCH v1 06/18] net/r8169: add phy registers access routines
Date: Tue, 15 Oct 2024 05:10:48 +0200 (CEST) [thread overview]
Message-ID: <20241015031048.8D62E120757@dpdk.org> (raw)
In-Reply-To: <20241015030928.70642-7-howard_wang@realsil.com.cn>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/145936
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
CHECK:CAMELCASE: Avoid CamelCase: <RegNum>
#94: FILE: drivers/net/r8169/r8169_phy.c:43:
+rtl_map_phy_ocp_addr(u16 PageNum, u8 RegNum)
CHECK:BRACES: braces {} should be used on all arms of this statement
#110: FILE: drivers/net/r8169/r8169_phy.c:59:
+ if (ocp_reg_num < 16)
[...]
+ else {
[...]
CHECK:BRACES: Unbalanced braces around else statement
#112: FILE: drivers/net/r8169/r8169_phy.c:61:
+ else {
CHECK:CAMELCASE: Avoid CamelCase: <RegAddr>
#123: FILE: drivers/net/r8169/r8169_phy.c:72:
+rtl_mdio_real_read_phy_ocp(struct rtl_hw *hw, u32 RegAddr)
CHECK:CAMELCASE: Avoid CamelCase: <OCPR_Addr_Reg_shift>
#129: FILE: drivers/net/r8169/r8169_phy.c:78:
+ data32 <<= OCPR_Addr_Reg_shift;
CHECK:CAMELCASE: Avoid CamelCase: <OCPR_Flag>
#135: FILE: drivers/net/r8169/r8169_phy.c:84:
+ if (RTL_R32(hw, PHYOCP) & OCPR_Flag)
CHECK:CAMELCASE: Avoid CamelCase: <OCPDR_Data_Mask>
#138: FILE: drivers/net/r8169/r8169_phy.c:87:
+ value = RTL_R32(hw, PHYOCP) & OCPDR_Data_Mask;
CHECK:CAMELCASE: Avoid CamelCase: <OCPR_Write>
#173: FILE: drivers/net/r8169/r8169_phy.c:122:
+ data32 |= OCPR_Write | value;
ERROR:CODE_INDENT: code indent should use tabs where possible
#222: FILE: drivers/net/r8169/r8169_phy.c:171:
+ u16 setmask)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#222: FILE: drivers/net/r8169/r8169_phy.c:171:
+ u16 setmask)$
CHECK:CAMELCASE: Avoid CamelCase: <EPHYAR_Write>
#249: FILE: drivers/net/r8169/r8169_phy.c:198:
+ RTL_W32(hw, EPHYAR, EPHYAR_Write |
ERROR:CODE_INDENT: code indent should use tabs where possible
#250: FILE: drivers/net/r8169/r8169_phy.c:199:
+^I (addr & EPHYAR_Reg_Mask_v2) << EPHYAR_Reg_shift |$
CHECK:CAMELCASE: Avoid CamelCase: <EPHYAR_Reg_Mask_v2>
#250: FILE: drivers/net/r8169/r8169_phy.c:199:
+ (addr & EPHYAR_Reg_Mask_v2) << EPHYAR_Reg_shift |
CHECK:CAMELCASE: Avoid CamelCase: <EPHYAR_Reg_shift>
#250: FILE: drivers/net/r8169/r8169_phy.c:199:
+ (addr & EPHYAR_Reg_Mask_v2) << EPHYAR_Reg_shift |
ERROR:CODE_INDENT: code indent should use tabs where possible
#251: FILE: drivers/net/r8169/r8169_phy.c:200:
+^I (value & EPHYAR_Data_Mask));$
CHECK:CAMELCASE: Avoid CamelCase: <EPHYAR_Data_Mask>
#251: FILE: drivers/net/r8169/r8169_phy.c:200:
+ (value & EPHYAR_Data_Mask));
CHECK:USLEEP_RANGE: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
#254: FILE: drivers/net/r8169/r8169_phy.c:203:
+ udelay(100);
CHECK:CAMELCASE: Avoid CamelCase: <EPHYAR_Flag>
#257: FILE: drivers/net/r8169/r8169_phy.c:206:
+ if (!(RTL_R32(hw, EPHYAR) & EPHYAR_Flag))
CHECK:USLEEP_RANGE: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
#261: FILE: drivers/net/r8169/r8169_phy.c:210:
+ udelay(20);
CHECK:CAMELCASE: Avoid CamelCase: <EPHYAR_Read>
#270: FILE: drivers/net/r8169/r8169_phy.c:219:
+ RTL_W32(hw, EPHYAR, EPHYAR_Read | (addr & EPHYAR_Reg_Mask_v2) <<
ERROR:CODE_INDENT: code indent should use tabs where possible
#271: FILE: drivers/net/r8169/r8169_phy.c:220:
+^I EPHYAR_Reg_shift);$
CHECK:USLEEP_RANGE: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
#274: FILE: drivers/net/r8169/r8169_phy.c:223:
+ udelay(100);
CHECK:USLEEP_RANGE: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
#283: FILE: drivers/net/r8169/r8169_phy.c:232:
+ udelay(20);
ERROR:CODE_INDENT: code indent should use tabs where possible
#290: FILE: drivers/net/r8169/r8169_phy.c:239:
+ u16 setmask)$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#290: FILE: drivers/net/r8169/r8169_phy.c:239:
+ u16 setmask)$
ERROR:CODE_INDENT: code indent should use tabs where possible
#327: FILE: drivers/net/r8169/r8169_phy.h:27:
+ u16 clearmask, u16 setmask);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#327: FILE: drivers/net/r8169/r8169_phy.h:27:
+ u16 clearmask, u16 setmask);$
ERROR:CODE_INDENT: code indent should use tabs where possible
#334: FILE: drivers/net/r8169/r8169_phy.h:34:
+ u16 setmask);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#334: FILE: drivers/net/r8169/r8169_phy.h:34:
+ u16 setmask);$
total: 7 errors, 5 warnings, 18 checks, 252 lines checked
parent reply other threads:[~2024-10-15 3:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241015030928.70642-7-howard_wang@realsil.com.cn>]
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=20241015031048.8D62E120757@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).