Re: rio_init, tty_io call confusion. 2.4.8-pre4

[Alan Cox]

> drivers/char/tty_io calls rio_init and gets a link error when rio is
> linked into the kenrel because rio_init is declared as static.  However
> rio_init is also declared as module_init() so it gets called twice, one
> from tty_io and once from the kernel initcall code.  One of those calls
> has to go.  If you keep the tty_io call then rio_init cannot be static.

The tty_io call appears to be stale