Thread (6 messages) flat view 6 messages, 3 authors, 2025-10-28

Re: [PATCH] net: phy: motorcomm: Fix the issue in the code regarding the incorrect use of time units

From: Andrew Lunn <andrew@lunn.ch>
Date: 2025-10-28 12:07:52
Also in: stable

quoted
quoted
 #define YT8521_CCR_RXC_DLY_EN			BIT(8)
-#define YT8521_CCR_RXC_DLY_1_900_NS		1900
+#define YT8521_CCR_RXC_DLY_1_900_PS		1900
This could be down to interpretation.

#define YT8521_CCR_RXC_DLY_1.900_NS		1900

would be technically correct, but not valid for cpp(1). So the . is
replaced with a _ .

#define YT8521_CCR_RXC_DLY_1900_PS		1900

would also be correct, but that is not what you have in your patch,
you leave the _ in place.
Alright, I didn't realize that 1_950 represents 1.950;
I thought the underscores were used for code neatness,
making numbers like 900 and 1050 the same length, for example:
#define YT8521_RC1R_RGMII_0_900_PS
#define YT8521_RC1R_RGMII_1_050_PS

In that case, is my patch still necessary?
I think it is unnecessary.

If you want, you could add a comment which explains that the _ should
be read as a .  However, this does appear elsewhere in Linux, it is
one of those things you learn with time.

    Andrew

---
pw-bot: cr
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help