Hi David,
David Laight writes:
> From: Vivien Didelot
>> Sent: 13 October 2017 16:29
>> Vivien Didelot writes:
>>
>> >>> How about using:
>> >>>
>> >>> union {
>> >>> struct net_device *master;
>> >>> struct net_device *slave;
>> >>> } netdev;
>> >> ...
>> >>
>> >> You can
From: Vivien Didelot
> Sent: 13 October 2017 16:29
> Vivien Didelot writes:
>
> >>> How about using:
> >>>
> >>> union {
> >>> struct net_device *master;
> >>> struct net_device *slave;
> >>> } netdev;
> >> ...
> >>
> >> You can remove the 'netdev' all the compilers suppor
Hi again,
Vivien Didelot writes:
>>> How about using:
>>>
>>> union {
>>> struct net_device *master;
>>> struct net_device *slave;
>>> } netdev;
>> ...
>>
>> You can remove the 'netdev' all the compilers support unnamed unions.
>
> There are issues with older GCC
Hi David,
David Laight writes:
> From: Florian Fainelli
>> Sent: 13 October 2017 00:05
> ...
>> How about using:
>>
>> union {
>> struct net_device *master;
>> struct net_device *slave;
>> } netdev;
> ...
>
> You can remove the 'netdev' all the compilers supp
From: Florian Fainelli
> Sent: 13 October 2017 00:05
...
> How about using:
>
> union {
> struct net_device *master;
> struct net_device *slave;
> } netdev;
...
You can remove the 'netdev' all the compilers support unnamed unions.
David
Hi Florian,
Florian Fainelli writes:
> On 10/12/2017 03:51 PM, Vivien Didelot wrote:
>> The dsa_port structure has a "netdev" member, which can be used for
>> either the master device, or the slave device, depending on its type.
>>
>> It is true that today, CPU port are not exposed to userspace
On 10/12/2017 03:51 PM, Vivien Didelot wrote:
> The dsa_port structure has a "netdev" member, which can be used for
> either the master device, or the slave device, depending on its type.
>
> It is true that today, CPU port are not exposed to userspace, thus the
> port's netdev member can be used
7 matches
Mail list logo