Is the attached patch correct?
The kernel does not use code marked __exit/__exitdata, so it seems like
it can drop the data when it drops __init{data} data.
Regards,
Jeff
-- Custom driver development | Never worry about theory as long Open source programming | as the machinery does what it's | supposed to do. -- R. A. Heinlein --------------3163AF914E7E0D6B7C9A56C2 Content-Type: text/plain; charset=us-ascii; name="init.h.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="init.h.patch"--- linux.ac/include/linux/init.h Thu Aug 26 15:43:58 1999 +++ linux/include/linux/init.h Mon Sep 20 10:45:35 1999 @@ -68,9 +68,9 @@ * or exit time. */ #define __init __attribute__ ((__section__ (".text.init"))) -#define __exit __attribute__ ((unused, __section__(".text.init"))) +#define __exit __attribute__ ((__section__ (".text.init"))) #define __initdata __attribute__ ((__section__ (".data.init"))) -#define __exitdata __attribute__ ((unused, __section__ (".data.init"))) +#define __exitdata __attribute__ ((__section__ (".data.init"))) #define __initsetup __attribute__ ((unused,__section__ (".setup.init"))) #define __init_call __attribute__ ((unused,__section__ (".initcall.init")))
--------------3163AF914E7E0D6B7C9A56C2--
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/