forked from Minki/linux
a07ea4d994
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> |
||
---|---|---|
.. | ||
6lowpan | ||
core.c | ||
core.h | ||
header_ops.c | ||
ieee802154.h | ||
Kconfig | ||
Makefile | ||
netlink.c | ||
nl802154.c | ||
nl802154.h | ||
nl_policy.c | ||
nl-mac.c | ||
nl-phy.c | ||
rdev-ops.h | ||
socket.c | ||
sysfs.c | ||
sysfs.h | ||
trace.c | ||
trace.h |