All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] Add CRTC helper drm_crtc_from_index()
Date: Fri, 30 Dec 2016 12:16:43 +0100	[thread overview]
Message-ID: <20161230111643.GD2667@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <1483015290-16660-1-git-send-email-shawnguo@kernel.org>

On Thu, Dec 29, 2016 at 08:41:27PM +0800, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@linaro.org>
> 
> This is a suggestion from Sean Paul.  ZTE and Rockchip DRM drivers have
> the similar code to find registered CRTC by given index.  The series
> create a CRTC helper drm_crtc_from_index() to do the job, just like
> drm_plane_from_index() to search plane, and change ZTE, Rockchip driver
> to use the helper.
> 
> Shawn Guo (3):
>   drm: add crtc helper drm_crtc_from_index()
>   drm: zte: use crtc helper drm_crtc_from_index()
>   drm: rockchip: use crtc helper drm_crtc_from_index()

Entire series applied. I suspect that there's more drivers open-coding
something like this in their vblank code, might be worth it to grep for
them all and do a quick audit.

Thanks a lot,
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-12-30 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29 12:41 [PATCH 0/3] Add CRTC helper drm_crtc_from_index() Shawn Guo
2016-12-29 12:41 ` [PATCH 1/3] drm: add crtc " Shawn Guo
2016-12-30 11:14   ` Daniel Vetter
2016-12-29 12:41 ` [PATCH 2/3] drm: zte: use " Shawn Guo
2016-12-29 12:41 ` [PATCH 3/3] drm: rockchip: " Shawn Guo
2016-12-30 11:16 ` Daniel Vetter [this message]
2017-01-09  9:03   ` [PATCH 0/3] Add CRTC " Shawn Guo
2017-01-09  9:58     ` 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=20161230111643.GD2667@dvetter-linux.ger.corp.intel.com \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=shawnguo@kernel.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 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.