[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1445520883-13287-1-git-send-email-vivien.didelot@savoirfairelinux.com>
Date: Thu, 22 Oct 2015 09:34:37 -0400
From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To: netdev@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel@...oirfairelinux.com,
"David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Scott Feldman <sfeldma@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Subject: [PATCH net-next v4 0/6] net: dsa: implement port_fdb_dump in drivers
Not all switch chips provide a Get Next kind of operation to dump FDB entries.
It is preferred to let the driver handle the dump operation the way it works
best for the chip. Thus, drop port_fdb_getnext and implement the port_fdb_dump
operation in DSA, which pushes the switchdev FDB dump callback down to the
drivers. mv88e6xxx is the only driver affected and is updated accordingly.
v3 -> v4: fix rejects on latest net-next
v2 -> v3: opencode switchdev_obj_dump_cb_t to avoid multiple typedef;
use ether_addr_copy in fdb_dump
v1 -> v2: fix a few "return err" instead of "goto unlock" in mv88e6xxx.c
Vivien Didelot (6):
net: dsa: add port_fdb_dump function
net: dsa: mv88e6xxx: write VID outside of VTU Get Next code
net: dsa: mv88e6xxx: write MAC outside of ATU Get Next code
net: dsa: mv88e6xxx: implement port_fdb_dump
net: dsa: mv88e6xxx: remove port_fdb_getnext
net: dsa: remove port_fdb_getnext
drivers/net/dsa/mv88e6171.c | 2 +-
drivers/net/dsa/mv88e6352.c | 2 +-
drivers/net/dsa/mv88e6xxx.c | 132 ++++++++++++++++++++++++--------------------
drivers/net/dsa/mv88e6xxx.h | 5 +-
include/net/dsa.h | 7 ++-
net/dsa/slave.c | 26 +--------
6 files changed, 83 insertions(+), 91 deletions(-)
--
2.6.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists