[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61e316c5-e504-4ad1-93a3-f2df5a16b654@lunn.ch>
Date: Thu, 21 Sep 2023 21:19:30 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Parthiban.Veerasooran@...rochip.com
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
corbet@....net, Steen.Hegelund@...rochip.com, rdunlap@...radead.org,
horms@...nel.org, casper.casan@...il.com, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, Horatiu.Vultur@...rochip.com,
Woojung.Huh@...rochip.com, Nicolas.Ferre@...rochip.com,
UNGLinuxDriver@...rochip.com, Thorsten.Kummermehr@...rochip.com
Subject: Re: [RFC PATCH net-next 1/6] net: ethernet: implement OPEN Alliance
control transaction interface
> Yes, as "struct oa_tc6" and its members are not or going to be accessed
> in the MAC driver, I will consider this as an opaque structure and
> declare it as void *opaque_oa_tc6 in the MAC driver private structure
> "struct lan865x_priv" and will pass to the APIs exported from oa_tc6.c lib.
>
> Is my understanding correct?
Yes.
If the structure is going to be truly opaque, i suggest having it in
the C file, not the H file.
Andrew
Powered by blists - more mailing lists