Hi Viswas! >> Where are these parameters made visible? >> >> Also, why not make the phy_errcnt members __le32 instead of using >> __force? > > This was added to avoid sparse compiler warnings reported. Yes, but those warnings are indicative that your struct definitions are problematic. I suggest you have one struct with __le32 members which you use when querying the values from the hardware. And then another struct that's host-endian. Which goes back to my first question: Where are these phy parameters actually used and/or exposed to userland? -- Martin K. Petersen Oracle Linux Engineering
