From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm: Unexport drm_connector_register_all()
Date: Tue, 28 Jun 2016 11:14:12 +0300 [thread overview]
Message-ID: <874m8divcb.fsf@intel.com> (raw)
In-Reply-To: <20160628072543.GA31475@nuc-i3427.alporthouse.com>
On Tue, 28 Jun 2016, Chris Wilson <chris@chris-wilson.co.uk> 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 dynamic configuration changes.
Fair enough.
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-28 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:36 [PATCH 1/5] drm: Unexport drm_connector_register_all() Chris Wilson
2016-06-24 14:36 ` [PATCH 2/5] drm/sun4i: Remove redundant call to drm_connector_unregister_all() Chris Wilson
2016-06-24 14:36 ` [PATCH 3/5] drm: Do a full device unregister when unplugging Chris Wilson
2016-06-24 14:36 ` [PATCH 4/5] drm/udl: Unplugging a device now unregisters it Chris Wilson
2016-06-24 14:36 ` [PATCH 5/5] drm: Unexport drm_connector_unregister_all() Chris Wilson
2016-06-27 13:03 ` [PATCH 1/5] drm: Unexport drm_connector_register_all() Jani Nikula
2016-06-28 7:25 ` Chris Wilson
2016-06-28 8:14 ` Jani Nikula [this message]
2016-07-12 11:03 ` Daniel Vetter
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=874m8divcb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox