[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <874mab9q4n.fsf@ketchup.mtl.sfl>
Date: Fri, 06 May 2016 11:12:56 -0400
From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...oirfairelinux.com,
"David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [RFC PATCH net-next 14/20] net: dsa: mv88e6xxx: factorize VLAN Ethertype
Hi Andrew,
Andrew Lunn <andrew@...n.ch> writes:
>> @@ -55,6 +58,7 @@ static const struct mv88e6xxx_info mv88e6131_table[] = {
>> .num_databases = 256,
>> .num_ports = 10,
>> .flags = MV88E6XXX_FLAG_ATU |
>> + MV88E6XXX_FLAG_CORE_TAG_TYPE |
>> MV88E6XXX_FLAG_PPU |
>> MV88E6XXX_FLAG_VLANTABLE |
>> MV88E6XXX_FLAG_VTU,
>
> Rather than repeating these flags again and again, could you add one
> #define containing the flags, and then use that to initialise .flags.
Hum OK, I wasn't sure, but looking at the final mv88e6xxx_info table, I
can see that models from the same family all have the same set of flags,
even if they don't have the same number of ports or databases.
I'll add one MV88E6XXX_FLAGS_xxxx per family.
Thanks,
Vivien
Powered by blists - more mailing lists