diff options
author | 2009-06-12 21:46:50 -0600 | |
---|---|---|
committer | 2009-06-12 21:46:53 +0930 | |
commit | ab8e2eb722f1e5fcbd8181e3e9ef4e95c52124df (patch) | |
tree | 41db45ac5411221c6e581952f7842004e6db48a5 /include/linux/moduleparam.h | |
parent | block: fix kernel-doc in recent block/ changes (diff) | |
download | wireguard-linux-ab8e2eb722f1e5fcbd8181e3e9ef4e95c52124df.tar.xz wireguard-linux-ab8e2eb722f1e5fcbd8181e3e9ef4e95c52124df.zip |
cyber2000fb.c: use proper method for stopping unload if CONFIG_ARCH_SHARK
Russell explains the __module_get():
> cyber2000fb.c does it in its module initialization function
> to prevent the module (when built for Shark) from being unloaded. It
> does this because it's from the days of 2.2 kernels and no one bothered
> writing the module unload support for Shark.
Since 2.4, the correct answer has been to not define an unload fn.
Cc: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: alex@shark-linux.de
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'include/linux/moduleparam.h')
0 files changed, 0 insertions, 0 deletions