Johannes Berg 56989f6d85 genetlink: mark families as __ro_after_init ... Now genl_register_family() is the only thing (other than the users themselves, perhaps, but I didn't find any doing that) writing to the family struct. In all families that I found, genl_register_family() is only called from __init functions (some indirectly, in which case I've add __init annotations to clarifly things), so all can actually be marked __ro_after_init. This protects the data structure from accidental corruption. 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
..
Kconfig	team: introduce random mode	2013-03-06 14:55:20 -05:00
Makefile	team: introduce random mode	2013-03-06 14:55:20 -05:00
team_mode_activebackup.c	team: fill-up LAG changeupper info struct and pass it along	2015-12-03 11:49:26 -05:00
team_mode_broadcast.c	team: fill-up LAG changeupper info struct and pass it along	2015-12-03 11:49:26 -05:00
team_mode_loadbalance.c	team: loadbalance: push lacpdus to exact delivery	2016-08-26 13:08:59 -07:00
team_mode_random.c	team: fill-up LAG changeupper info struct and pass it along	2015-12-03 11:49:26 -05:00
team_mode_roundrobin.c	team: fill-up LAG changeupper info struct and pass it along	2015-12-03 11:49:26 -05:00
team.c	genetlink: mark families as __ro_after_init	2016-10-27 16:16:09 -04:00