Hi Greg, > Provide a function device_move() to move a device to a new parent device. Add > auxilliary functions kobject_move() and sysfs_move_dir(). > kobject_move() generates a new uevent of type KOBJ_MOVE, containing the > previous path (DEVPATH_OLD) in addition to the usual values. For this, a new > interface kobject_uevent_env() is created that allows to add further > environmental data to the uevent at the kobject layer.
has this one been tested? I don't get it working. I always get an EINVAL when trying to move the TTY device of a Bluetooth RFCOMM link around. And shouldn't device_move(dev, NULL) re-attach it to the virtual device tree instead of failing? Regards Marcel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
