On Thu, Sep 01, 2016 at 03:40:43PM -0700, Laura Abbott wrote: > > The current Ion ioctls lack a good way to tell what ioctls are > available. Introduce an ioctl to give an ABI version. This way when the > ABI inevitably gets screwed up userspace will have a way to tell what > version of the screw up is available. This worries me. Why do we need this? Shouldn't any "new" abi changes just add on, and not change existing ioctl structure calls? Or worst case, you remove an ioctl and then userspace "knows" that when the call fails. And who is the major userspace user of this interface? Who controls it? How are we keeping things in sync here? thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
