All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org,
	daniel.vetter@ffwll.ch
Subject: Re: [PATCH 1/3] drm: qxl: Let DRM core handle connector registering
Date: Tue, 17 Jan 2017 10:41:41 -0200	[thread overview]
Message-ID: <20170117124141.GN16017@joana> (raw)
In-Reply-To: <20170112161610.19924-1-krisman@collabora.co.uk>

Hi Gabriel,

2017-01-12 Gabriel Krisman Bertazi <krisman@collabora.co.uk>:

> Registering the connector explicitly right after creation is not
> necessary for modesetting drivers, because drm_dev_register already takes
> care of this on the core side, by calling drm_modeset_register_all.
> 
> In addition, performing the initialization too early will get in the way
> of the load() hook removal, because the connector interface cannot be
> published prior to registering the minors.
> 
> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
> CC: Dave Airlie <airlied@redhat.com>
> CC: Daniel Vetter <daniel.vetter@ffwll.ch>
> CC: dri-devel@lists.freedesktop.org
> ---
>  drivers/gpu/drm/qxl/qxl_display.c | 1 -
>  1 file changed, 1 deletion(-)

Applied to drm-misc-next. Thanks for the patch.

Gustavo

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2017-01-17 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 16:16 [PATCH 1/3] drm: qxl: Let DRM core handle connector registering Gabriel Krisman Bertazi
2017-01-12 16:16 ` [PATCH 2/3] drm: qxl: Open code probing sequence for qxl Gabriel Krisman Bertazi
2017-01-16 21:16   ` Gustavo Padovan
2017-01-17 13:15     ` Gabriel Krisman Bertazi
2017-01-12 16:16 ` [PATCH 3/3] drm: qxl: Open code teardown function " Gabriel Krisman Bertazi
2017-01-17 12:41 ` Gustavo Padovan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170117124141.GN16017@joana \
    --to=gustavo@padovan.org \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krisman@collabora.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.