On 07/18/2017 08:40 PM, Vivien Didelot wrote: > Hi Arkadi, > > Arkadi Sharshevsky <arka...@mellanox.com> writes: > >> The bridge port attributes/vlan for DSA devices should be set only >> from bridge code. Furthermore, The vlans are synced totally with the >> bridge so there is no need for special dump support. >> >> Signed-off-by: Arkadi Sharshevsky <arka...@mellanox.com> >> --- >> drivers/net/dsa/b53/b53_common.c | 44 -------------------------- >> drivers/net/dsa/b53/b53_priv.h | 3 -- >> drivers/net/dsa/bcm_sf2.c | 1 - >> drivers/net/dsa/dsa_loop.c | 38 ----------------------- >> drivers/net/dsa/microchip/ksz_common.c | 41 ------------------------- >> drivers/net/dsa/mv88e6xxx/chip.c | 56 >> ---------------------------------- >> include/net/dsa.h | 4 --- >> net/dsa/dsa_priv.h | 4 --- >> net/dsa/port.c | 12 -------- >> net/dsa/slave.c | 6 ---- > > Regarding this massive deletion, can you please split it in two patches, > one deleting first the DSA core usage of .port_vlan_dump, i.e. in: > > net/dsa/dsa_priv.h > net/dsa/port.c > net/dsa/slave.c > > Then a second patch which deletes the .port_vlan_dump implementations? > > This may sound useless but it will actually make it easy for us to > restore the VLAN dump support in drivers once we introduce an > alternative way to query the hardware. > > > Thanks, > > Vivien >
Yeah, no problem. But doesn't it make more sense to remove it first from the drivers and then from core? If it will be removed from core first it will leave unused code behind in the driver. Furthermore, it is symmetric with the code adding. You first add the core implementation and then only the drivers.
