From: Scott Feldman <sfeldma@gmail.com>
Date: Thu, 4 Jun 2015 03:43:42 +0000 (-0700)
Subject: switchdev: documentation: for static FDB ops, use switchdev_port_fdb_xxx ops
X-Git-Tag: v4.9.8~4072^2~138^2~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4b5364fbdce7e4b947e6e76d7341675ea2e12f4d;p=platform%2Fkernel%2Flinux-rpi3.git

switchdev: documentation: for static FDB ops, use switchdev_port_fdb_xxx ops

Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Acked-by: Jiri Pirko <jiri@resnulli.us>
Signed-off-by: David S. Miller <davem@davemloft.net>
---

diff --git a/Documentation/networking/switchdev.txt b/Documentation/networking/switchdev.txt
index 0554b68..00c703c 100644
--- a/Documentation/networking/switchdev.txt
+++ b/Documentation/networking/switchdev.txt
@@ -177,6 +177,10 @@ entries are installed, for example, using iproute2 bridge cmd:
 
 	bridge fdb add ADDR dev DEV [vlan VID] [self]
 
+The driver should use the helper switchdev_port_fdb_xxx ops for ndo_fdb_xxx
+ops, and handle add/delete/dump of SWITCHDEV_OBJ_PORT_FDB object using
+switchdev_port_obj_xxx ops.
+
 XXX: what should be done if offloading this rule to hardware fails (for
 example, due to full capacity in hardware tables) ?