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
..
af_netlink.c	netlink: do not enter direct reclaim from netlink_dump()	2016-10-06 20:53:13 -04:00
af_netlink.h	net/netlink/af_netlink.h: Remove unused structure.	2016-06-09 22:26:24 -07:00
diag.c	netlink: don't forget to release a rhashtable_iter structure	2016-09-07 17:29:38 -07:00
genetlink.c	genetlink: no longer support using static family IDs	2016-10-27 16:16:09 -04:00
Kconfig	netlink: remove mmapped netlink support	2016-02-18 11:42:18 -05:00
Makefile	netlink: Diag core and basic socket info dumping (v2)	2013-03-21 12:38:03 -04:00