Hello!
Which is a good thing, right? "driver_data" is usually a pointer to somewhere. Having userspace specify it would not be a good thing.
That depends on the driver usage, and the patch allows it to be configurable and defaults to not being used.
Maybe we could just define the operation as cloning of an entry for another device ID, including its driver_data.
Possibly. That would potentially require a lot of parameters to userspace. We would really need to duplicate all the currently existing sysfs parms to accomplish this.
-- Brian King eServer Storage I/O IBM Linux Technology Center - 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/
