Hi Brian, > This patch fixes the device removal order when a connection is closed, > which allows HAL to see the remove event and prevents a bunch of > duplicate devices from piling up and eventually hitting the limit for > the for input devices in X. > > Posting for discussion since I used a polling loop (with a sleep) to > wait for child devices to go away. I assume it'd be preferable to wait > in a more proper way. In that case, before I start, is this the right > place to be waiting? since this is executed in a workqueue, you could easily sleep here without any problems. However why do you need to sleep at all. The device_move should sleep until the device is moved away, doesn't it? Kay, David, wouldn't be pinning of the parent device here be enough to get this done in a clean way? Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
