On Fri, Jun 24, 2016 at 03:36:18PM +0100, Chris Wilson wrote:
> This has now been removed from all drivers as it is performed centrally
> as a part of device registration for modesetting drivers. With the last
> user gone, we can unexport it from the DRM module.
>
> Signed-off-by: Chris Wilson
>
On Tue, 28 Jun 2016, Chris Wilson wrote:
>> Bikeshed, why throw away the documentation when you could just tweak it
>> to reflect reality?
>
> Because Daniel only wanted the public interface in the DRM docs to avoid
> confusion. Drivers should only be calling drm_connector_register to
> handle dyn
On Mon, Jun 27, 2016 at 04:03:23PM +0300, Jani Nikula wrote:
> On Fri, 24 Jun 2016, Chris Wilson wrote:
> > This has now been removed from all drivers as it is performed centrally
> > as a part of device registration for modesetting drivers. With the last
> > user gone, we can unexport it from the
On Fri, 24 Jun 2016, Chris Wilson wrote:
> This has now been removed from all drivers as it is performed centrally
> as a part of device registration for modesetting drivers. With the last
> user gone, we can unexport it from the DRM module.
>
> Signed-off-by: Chris Wilson
> Cc: David Airlie
> C
This has now been removed from all drivers as it is performed centrally
as a part of device registration for modesetting drivers. With the last
user gone, we can unexport it from the DRM module.
Signed-off-by: Chris Wilson
Cc: David Airlie
Cc: Daniel Vetter
Cc: dri-devel at lists.freedesktop.or
