![]() | |||||||||||||
Messages in this thread |
In message <Pine.LNX.4.44.0306241851550.11817-100000@serv> you write:
> Hi,
> On Mon, 23 Jun 2003, Rusty Russell wrote:
>
> > D: One longstanding complaint is that modules can only have one
> > D: module_init, and one module_exit (builtin code can have multiple
> > D: __initcall however). This means, for example, that it is not
> > D: possible to write a "module_proc_entry(name, readfn)" function
> > D: which can be used like so:
> > D:
> > D: module_init(myinitfn);
> > D: module_cleanup(myinitfn);
> > D: module_proc_entry("some/path/foo", read_foo);
>
> What happens if a module is compiled into the kernel and one of the init
> functions fails?
We ignore the failure, as we do with initcalls at the moment. I
wasn't really intending to deprecate the existing mechanisms: this is
simple at least 8)
Hmm, were you thinking of grouping by KBUILD_BASENAME? Can you think
of a case where that would be nicer to use?
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
| ||||||||||||
| Last update: 2005-03-22 12:36 [W:0.176 / U:0.010 seconds] ©2003-2008 Jasper Spaans | |||||||||||||