[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ha8w50s9.fsf@rustcorp.com.au>
Date: Wed, 22 Jan 2014 10:46:06 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: Paul Gortmaker <paul.gortmaker@...driver.com>,
linux-kernel@...r.kernel.org
Cc: linux-arch@...r.kernel.org,
Paul Gortmaker <paul.gortmaker@...driver.com>
Subject: Re: [PATCH 31/73] module: relocate module_init from init.h to module.h
Paul Gortmaker <paul.gortmaker@...driver.com> writes:
> Modular users will always be users of init functionality, but
> users of init functionality are not necessarily always modules.
>
> Hence any functionality like module_init and module_exit would
> be more at home in the module.h file. And module.h should
> explicitly include init.h to make the dependency clear.
>
> We've already done all the legwork needed to ensure that this
> move does not cause any build regressions due to implicit
> header file include assumptions about where module_init lives.
>
> Cc: Rusty Russell <rusty@...tcorp.com.au>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
Acked-by: Rusty Russell <rusty@...tcorp.com.au>
Want to delete the extraneous semicolons, for bonus points? :)
> +#define module_init(x) __initcall(x);
...
> +#define module_exit(x) __exitcall(x);
Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists