regarding drivers/parport/*
is there any particular reason as to why the different parport drivers
aren't initialized using module_init() ? Like weird init order
dependencies and stuff.
Looking at parport_init itself (which has hardcoded init calls to the
different drivers right now) it does not look like it does anything
particularly special except some proc filesystem registering.
Is it just because nobody has gotten around to "fixing" it or is there a
deeper reason ?
Regards
Bjorn
-
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/