On Thu, Oct 17, 2013 at 12:34 PM, <ville.syrjala@xxxxxxxxxxxxxxx> wrote: > We're rather inconsistent in which error values we return to userspace > on failure. I want to unify the behaviour a bit and consistently return > ENOENT when mode object lookups fail. We already do that in a few places > but in most places we just return EINVAL. > > I made a separate patch for each affected driver just in case there's some > magic meaning to the error values for certain drivers. > > > Ville Syrjälä (7): > drm: Consistently return -ENOENT when a mode object can't be found > drm: Return -ENOENT when a framebuffer can't be found > drm/gma500: Return -ENOENT when a mode object can't be found > drm/i915: Return -ENOENT when a mode object can't be found > drm/radeon: Return -ENOENT when a mode object can't be found > drm/vmwgfx: Return -ENOENT when a mode object can't be found > drm/vmwgfx: Return -ENOENT when a framebuffer can't be found Sounds good to me, vmwgfx patches are: Reviewed-By: Jakob Bornecrantz <jakob@xxxxxxxxxx> Cheers, Jakob. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
