device_for_each_child() before device_add() doesn't work

[David Vrabel]

Calling device_for_each_child() on a device that has yet to be added
(with device_add()) used to work.  UWB subsystem currently tries to do this.

Since "driver core: move klist_children into private structure"[1] this
no longer works (an oops occurs in device_for_each_chid()).  Is it
something that ought to work? Or should the UWB subsystem be changed to
not do this?

David

[1] f791b8c836307b58cbf62133a6a772ed1a92fb33
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/