diff options
| author | Johannes Berg <johannes.berg@intel.com> | 2016-10-24 14:40:05 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-10-27 16:16:09 -0400 |
| commit | 56989f6d8568c21257dcec0f5e644d5570ba3281 (patch) | |
| tree | 60a6b44865e68e25dbc8bcc38d0000e12106f2d8 /drivers/irqchip | |
| parent | 2ae0f17df1cd52aafd1ab0415ea1f1dd56dc0e2a (diff) | |
| download | linux-56989f6d8568c21257dcec0f5e644d5570ba3281.tar.gz linux-56989f6d8568c21257dcec0f5e644d5570ba3281.tar.bz2 linux-56989f6d8568c21257dcec0f5e644d5570ba3281.zip | |
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>
Diffstat (limited to 'drivers/irqchip')
0 files changed, 0 insertions, 0 deletions