On Mon, Jan 27, 2020 at 01:14:37PM +0100, Thomas Hellström (VMware) wrote: > On 1/27/20 11:02 AM, Daniel Vetter wrote: > > vmwgfx stopped using them. > > > > With the drm device model that we've slowly evolved over the past few > > years master status essentially controls access to display resources, > > and nothing else. Since that's a pure access permission check drivers > > should have no need at all to track additional state on a per file > > basis. > > > > Aside: For cleanup and restoring kernel-internal clients the grand > > plan is to move everyone over to drm_client and > > drm_master_internal_acquire/release, like the generic fbdev code > > already does. That should get rid of most ->lastclose implementations, > > and I think also subsumes any processing vmwgfx does in > > master_set/drop. > > > > Cc: "Thomas Hellström (VMware)" <thomas_os@xxxxxxxxxxxx> > > Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxxx> > > Reviewed-by: Thomas Hellstrom <thellstrom@xxxxxxxxxx> Thanks for your review, patch applied. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
