[lkml]   [2009]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectdevice_for_each_child() before device_add() doesn't work
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?


[1] f791b8c836307b58cbf62133a6a772ed1a92fb33
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park, Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ

 \ /
  Last update: 2009-04-14 18:59    [W:0.057 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site