Re: [Intel-gfx] [PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

2017-04-17 Thread Daniel Vetter
On Fri, Apr 14, 2017 at 6:20 PM, Mike Lothian wrote: > Hi > > X no longer starts for me and I've bisected it back to this commit > > During bisect I ended up on commits where my laptop would lockup during boot The bugfix the hangs is in linux-next, but hasn't landed in drm-next yet: commit 8cb68

Re: [Intel-gfx] [PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

2017-04-14 Thread Mike Lothian
Hi X no longer starts for me and I've bisected it back to this commit During bisect I ended up on commits where my laptop would lockup during boot Regards Mike On Tue, 4 Apr 2017 at 06:39 Daniel Vetter wrote: > On Tue, Apr 4, 2017 at 12:13 AM, kbuild test robot wrote: > > [if your patch is

Re: [Intel-gfx] [PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

2017-04-03 Thread Daniel Vetter
On Tue, Apr 4, 2017 at 12:13 AM, kbuild test robot wrote: > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] It should compile just fine on latest linux-next (if there is one) where this code in vmwgfx is already removed. Well you just need the

Re: [Intel-gfx] [PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

2017-04-03 Thread kbuild test robot
Hi Daniel, [auto build test ERROR on next-20170330] [cannot apply to drm/drm-next drm-intel/for-linux-next robclark/msm-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc5] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-

[PATCH 02/15] drm: Remove drm_modeset_(un)lock_crtc

2017-04-03 Thread Daniel Vetter
The last user, the cursor ioctl, can just open-code this too. We simply have to move the acquire ctx dance from the universal function up into the top-level ioctl handler. Reviewed-by: Harry Wentland Signed-off-by: Daniel Vetter --- drivers/gpu/drm/drm_crtc_internal.h | 3 -- drivers/gpu/drm/d