Re: [Intel-gfx] [PATCH 2/3] drm: Sync errno values for property lookup errors

2019-01-29 Thread Daniel Vetter
On Fri, Jan 25, 2019 at 11:01:48PM +0200, Ville Syrjälä wrote: > On Tue, Jan 22, 2019 at 10:39:38AM +0100, Daniel Vetter wrote: > > On Mon, Jan 21, 2019 at 10:24:29PM +0200, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > Use ENOENT consistently for the case where the requested

Re: [Intel-gfx] [PATCH 2/3] drm: Sync errno values for property lookup errors

2019-01-25 Thread Ville Syrjälä
On Tue, Jan 22, 2019 at 10:39:38AM +0100, Daniel Vetter wrote: > On Mon, Jan 21, 2019 at 10:24:29PM +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Use ENOENT consistently for the case where the requested property > > isn't found, and EINVAL for the case where the object has no > >

Re: [Intel-gfx] [PATCH 2/3] drm: Sync errno values for property lookup errors

2019-01-22 Thread Daniel Vetter
On Mon, Jan 21, 2019 at 10:24:29PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Use ENOENT consistently for the case where the requested property > isn't found, and EINVAL for the case where the object has no > properties whatsoever. Currenrly these are handled differently > in the

[PATCH 2/3] drm: Sync errno values for property lookup errors

2019-01-21 Thread Ville Syrjala
From: Ville Syrjälä Use ENOENT consistently for the case where the requested property isn't found, and EINVAL for the case where the object has no properties whatsoever. Currenrly these are handled differently in the atomic and legacy codepaths. Signed-off-by: Ville Syrjälä ---