From: "Luis R. Rodriguez" <[email protected]> This is a no-op for the modular use case of the backports project but by enabling this it allows for developers a way to embed the backports releases onto a target source Linux directory, with obvious pending modifications, by adding our backport_init() onto the target kernel's init/main.c start_kernel().
Enable this theoretical use case. Hackers welcome to go play on this theoretical integration strategy now. Cc: [email protected] Signed-off-by: Luis R. Rodriguez <[email protected]> --- backport/compat/main.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/backport/compat/main.c b/backport/compat/main.c index 90ce751..b7dff1a 100644 --- a/backport/compat/main.c +++ b/backport/compat/main.c @@ -69,7 +69,7 @@ static int __init backport_init(void) return 0; } -module_init(backport_init); +subsys_initcall(backport_init); static void __exit backport_exit(void) { @@ -78,5 +78,4 @@ static void __exit backport_exit(void) return; } -module_exit(backport_exit); - +__exitcall(backport_exit); -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
