dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Do not set connector->encoder in drivers
Date: Tue, 17 Nov 2015 16:58:25 +0200	[thread overview]
Message-ID: <877flgekq6.fsf@intel.com> (raw)
In-Reply-To: <1447694393-24700-1-git-send-email-thierry.reding@gmail.com>

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.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-11-17 14:54 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 [this message]
2015-11-17 16:16   ` Daniel Vetter
2016-01-14 18:54   ` Laurent Pinchart

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=877flgekq6.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=thierry.reding@gmail.com \
    /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