mochel@osdl.org said:
> I don't see how your patch adresses chaining; there is only one
> notifier per bus type.
Well, you can do it by storing the pointer privately and hijacking it.
However, I think we'd use the existing kernel notifier chain stuff for that if
it is valuable.
> Along they way, we've found several things stand in the way of making
> this a smooth transition, so the plan is to stick with the bus
> intermediaries until the infrastructure matures enough to tackle
> those problems more easily.
I'm happy with keeping probe and remove in the bus specific driver template
and having the <bustype>_add_driver install generic device probe and remove
routines to handle these cases. My point was that the docs implied I should
use the generic driver probe and remove routines, which I can't without some
type of functionality like this.
If you envisage us never eliminating the driver specific probe and remove
routines, I'm happy. I'm less happy if there will come a day when I have to
revisit all the converted drivers to do the elimination.
James
-
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/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:23 EST