From: Daniel Vetter <daniel@ffwll.ch>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Thomas Wood <thomas.wood@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm: add register and unregister functions for connectors
Date: Thu, 19 Jun 2014 08:57:21 +0200 [thread overview]
Message-ID: <20140619065721.GM5821@phenom.ffwll.local> (raw)
In-Reply-To: <CANq1E4RgDsMtKQsCCiz4vJnpRiYmcDVTyqKyAm8FJBacQTLjpA@mail.gmail.com>
On Tue, Jun 10, 2014 at 06:21:35PM +0200, David Herrmann wrote:
> Hi
>
> On Thu, May 29, 2014 at 5:57 PM, Thomas Wood <thomas.wood@intel.com> wrote:
> > Introduce generic functions to register and unregister connectors. This
> > provides a common place to add and remove associated user space
> > interfaces.
> >
> > Signed-off-by: Thomas Wood <thomas.wood@intel.com>
> > ---
> > Documentation/DocBook/drm.tmpl | 6 +++---
> > drivers/gpu/drm/armada/armada_output.c | 4 ++--
> > drivers/gpu/drm/ast/ast_mode.c | 4 ++--
> > drivers/gpu/drm/bridge/ptn3460.c | 2 +-
> > drivers/gpu/drm/drm_crtc.c | 30 ++++++++++++++++++++++++++-
> > drivers/gpu/drm/drm_sysfs.c | 2 --
> > drivers/gpu/drm/exynos/exynos_dp_core.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_drm_connector.c | 6 +++---
> > drivers/gpu/drm/exynos/exynos_drm_dpi.c | 4 ++--
> > drivers/gpu/drm/exynos/exynos_drm_dsi.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_drm_vidi.c | 2 +-
> > drivers/gpu/drm/exynos/exynos_hdmi.c | 2 +-
> > drivers/gpu/drm/gma500/cdv_intel_crt.c | 4 ++--
> > drivers/gpu/drm/gma500/cdv_intel_dp.c | 4 ++--
> > drivers/gpu/drm/gma500/cdv_intel_hdmi.c | 4 ++--
> > drivers/gpu/drm/gma500/cdv_intel_lvds.c | 4 ++--
> > drivers/gpu/drm/gma500/mdfld_dsi_output.c | 4 ++--
> > drivers/gpu/drm/gma500/oaktrail_hdmi.c | 2 +-
> > drivers/gpu/drm/gma500/oaktrail_lvds.c | 2 +-
> > drivers/gpu/drm/gma500/psb_intel_lvds.c | 4 ++--
> > drivers/gpu/drm/gma500/psb_intel_sdvo.c | 4 ++--
> > drivers/gpu/drm/i915/intel_crt.c | 2 +-
> > drivers/gpu/drm/i915/intel_display.c | 2 +-
> > drivers/gpu/drm/i915/intel_dp.c | 4 ++--
> > drivers/gpu/drm/i915/intel_dsi.c | 2 +-
> > drivers/gpu/drm/i915/intel_dvo.c | 2 +-
> > drivers/gpu/drm/i915/intel_hdmi.c | 2 +-
> > drivers/gpu/drm/i915/intel_lvds.c | 2 +-
> > drivers/gpu/drm/i915/intel_sdvo.c | 10 ++++-----
> > drivers/gpu/drm/i915/intel_tv.c | 2 +-
> > drivers/gpu/drm/mgag200/mgag200_mode.c | 2 +-
> > drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 4 ++--
> > drivers/gpu/drm/nouveau/nouveau_connector.c | 4 ++--
> > drivers/gpu/drm/omapdrm/omap_connector.c | 4 ++--
> > drivers/gpu/drm/qxl/qxl_display.c | 4 ++--
> > drivers/gpu/drm/radeon/radeon_connectors.c | 6 +++---
> > drivers/gpu/drm/rcar-du/rcar_du_lvdscon.c | 4 ++--
> > drivers/gpu/drm/rcar-du/rcar_du_vgacon.c | 4 ++--
> > drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 6 +++---
> > drivers/gpu/drm/tegra/output.c | 4 ++--
> > drivers/gpu/drm/tilcdc/tilcdc_panel.c | 2 +-
> > drivers/gpu/drm/tilcdc/tilcdc_slave.c | 2 +-
> > drivers/gpu/drm/tilcdc/tilcdc_tfp410.c | 2 +-
> > drivers/gpu/drm/udl/udl_connector.c | 4 ++--
> > drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 2 +-
> > drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 2 +-
> > drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 2 +-
> > drivers/staging/imx-drm/imx-drm-core.c | 6 +++---
>
> You even caught imx.. and you removed the EXPORT_SYMBOL. So looks all
> good to me.
> I like that refactoring and I don't think we need an ACK from all
> driver authors. This is:
>
> Reviewed-by: David Herrmann <dh.herrmann@gmail.com>
>
> Maybe Daniel or Dave can pick this up?
I've pulled in all three patches into my topic/core-stuff branch and will
send a pull request to Dave once drm-next is open.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-06-19 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 15:57 [PATCH 0/3] connector debugfs properties Thomas Wood
2014-05-29 15:57 ` [PATCH 1/3] drm: add register and unregister functions for connectors Thomas Wood
2014-06-10 16:21 ` David Herrmann
2014-06-19 6:57 ` Daniel Vetter [this message]
2014-05-29 15:57 ` [PATCH 2/3] drm/debugfs: add a "force" file per connector Thomas Wood
2014-06-10 16:36 ` David Herrmann
2014-06-18 16:52 ` [PATCH v2 0/2] connector debugfs properties Thomas Wood
2014-06-18 16:52 ` [PATCH v2 1/2] drm/debugfs: add a "force" file per connector Thomas Wood
2014-06-18 20:11 ` Alex Deucher
2014-06-18 16:52 ` [PATCH v2 2/2] drm/debugfs: add an "edid_override" " Thomas Wood
2014-06-18 19:37 ` Alex Deucher
2014-06-18 20:08 ` [Intel-gfx] " Daniel Vetter
2014-05-29 15:57 ` [PATCH 3/3] " Thomas Wood
2014-06-10 16:58 ` David Herrmann
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=20140619065721.GM5821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@intel.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