![]() | |||||||||||||
Messages in this thread |
On Tue, 14 Nov 2006 22:50:52 -0800, Greg KH <greg@kroah.com> wrote: > On Tue, Nov 14, 2006 at 11:32:08AM +0100, Cornelia Huck wrote: > > From: Cornelia Huck <cornelia.huck@de.ibm.com> > > > > Provide a function device_move() to move a device to a new parent device. Add > > auxilliary functions kobject_move() and sysfs_move_dir(). > > At first glance, this looks sane, but for the kobject_move function, we > are not notifying userspace that something has changed here. > > Is that ok? > > How will udev and HAL handle something like this without being told > about it? When the device eventually goes away, I think they will be > very confused. Hm. I don't think we want to trigger udev with some remove/add events (especially since it is still the same device, it just has been moved around). A change event doesn't sound quite right either. But I guess we need to do something, at least to make HAL happy since it remembers the path in sysfs (although I seem to remember a HAL patch that got rid of it?) -- Cornelia Huck Linux for zSeries Developer Tel.: +49-7031-16-4837, Mail: cornelia.huck@de.ibm.com - 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/ | ||||||||||||
| Last update: 2006-11-15 08:31 [from the cache] ©2003-2008 | |||||||||||||