From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Liviu Dudau <Liviu.Dudau@arm.com>,
dri-devel@lists.freedesktop.org,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH] drm: Do not set connector->encoder in drivers
Date: Thu, 14 Jan 2016 20:54:13 +0200 [thread overview]
Message-ID: <1759010.tgOCoHNKnY@avalon> (raw)
In-Reply-To: <877flgekq6.fsf@intel.com>
On Tuesday 17 November 2015 16:58:25 Jani Nikula wrote:
> On Mon, 16 Nov 2015, Thierry Reding <thierry.reding@gmail.com> wrote:
> > An encoder is associated with a connector by the DRM core as a result of
> > setting up a configuration. Drivers using the atomic or legacy helpers
> > should never set up this link, even if it is a static one.
>
> Not to block this patch in any way, but really this kind of stuff should
> end up in the struct drm_connector kernel-doc. Although it's already a
> monster.
I was about to mention the same, so I'll second. And v4.4 is here, so we can
deal with the monster :-)
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-01-14 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 17:19 [PATCH] drm: Do not set connector->encoder in drivers Thierry Reding
2015-11-16 17:46 ` Russell King - ARM Linux
2015-11-17 10:43 ` Daniel Vetter
2015-11-17 10:29 ` Liviu Dudau
2016-01-13 11:47 ` Liviu Dudau
2016-01-13 12:31 ` Daniel Vetter
2015-11-17 10:46 ` Daniel Vetter
2015-11-17 14:58 ` Jani Nikula
2015-11-17 16:16 ` Daniel Vetter
2016-01-14 18:54 ` Laurent Pinchart [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=1759010.tgOCoHNKnY@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Liviu.Dudau@arm.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=rmk+kernel@arm.linux.org.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.