linux-bl808/net/openvswitch
Johannes Berg a07ea4d994 genetlink: no longer support using static family IDs
Static family IDs have never really been used, the only
use case was the workaround I introduced for those users
that assumed their family ID was also their multicast
group ID.

Additionally, because static family IDs would never be
reserved by the generic netlink code, using a relatively
low ID would only work for built-in families that can be
registered immediately after generic netlink is started,
which is basically only the control family (apart from
the workaround code, which I also had to add code for so
it would reserve those IDs)

Thus, anything other than GENL_ID_GENERATE is flawed and
luckily not used except in the cases I mentioned. Move
those workarounds into a few lines of code, and then get
rid of GENL_ID_GENERATE entirely, making it more robust.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-10-27 16:16:09 -04:00
..
actions.c openvswitch: correctly fragment packet with mpls headers 2016-10-12 01:42:52 -04:00
conntrack.c
conntrack.h
datapath.c genetlink: no longer support using static family IDs 2016-10-27 16:16:09 -04:00
datapath.h
dp_notify.c
flow.c openvswitch: vlan: remove wrong likely statement 2016-10-13 10:03:23 -04:00
flow.h
flow_netlink.c
flow_netlink.h
flow_table.c
flow_table.h
Kconfig
Makefile
vport-geneve.c
vport-gre.c
vport-internal_dev.c net: use core MTU range checking in core net infra 2016-10-20 14:51:09 -04:00
vport-internal_dev.h
vport-netdev.c openvswitch: remove unnecessary EXPORT_SYMBOLs 2016-10-19 15:11:55 -04:00
vport-netdev.h
vport-vxlan.c
vport.c openvswitch: remove unnecessary EXPORT_SYMBOLs 2016-10-19 15:11:55 -04:00
vport.h openvswitch: remove unused functions 2016-10-19 15:11:55 -04:00