[PATCH 15/16] drm: Clear up master tracking booleans

[Chris Wilson]

On Fri, Jun 17, 2016 at 09:33:33AM +0200, Daniel Vetter wrote:
> - is_master can be removed, we can compute this by checking allowed_master
>   (which really just tracks whether a master struct has been allocated
>   for this fpriv in either open or set_master), and whether the fpriv is
>   the current master on the device.
> 
> - that frees up is_master as a good replacement name for allowed_master.
>   With that it's clear that it tracks whether the fpriv is a master (with
>   possibly clients attached to it and authenticated against it), and that
>   one of those fprivs with is_master set is the current master.
> 
> Cc: Chris Wilson <chris at chris-wilson.co.uk>
> Cc: Thomas Hellstrom <thellstrom at vmware.com>
> Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>
Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre