public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 1/5] drm/i915: Use new atomic iterator macros in ddi
Date: Thu,  9 Mar 2017 15:52:01 +0100	[thread overview]
Message-ID: <1489071125-917-2-git-send-email-maarten.lankhorst@linux.intel.com> (raw)
In-Reply-To: <1489071125-917-1-git-send-email-maarten.lankhorst@linux.intel.com>

Use for_each_new_connector_in_state instead of for_each_connector_in_state.
Also make the function static, it's only used inside intel_ddi.c

Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
 drivers/gpu/drm/i915/intel_ddi.c | 4 ++--
 drivers/gpu/drm/i915/intel_drv.h | 2 --
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
index 04676760e6fd..4da81d4ae166 100644
--- a/drivers/gpu/drm/i915/intel_ddi.c
+++ b/drivers/gpu/drm/i915/intel_ddi.c
@@ -837,7 +837,7 @@ intel_ddi_get_crtc_encoder(struct intel_crtc *crtc)
 	return ret;
 }
 
-struct intel_encoder *
+static struct intel_encoder *
 intel_ddi_get_crtc_new_encoder(struct intel_crtc_state *crtc_state)
 {
 	struct intel_crtc *crtc = to_intel_crtc(crtc_state->base.crtc);
@@ -850,7 +850,7 @@ intel_ddi_get_crtc_new_encoder(struct intel_crtc_state *crtc_state)
 
 	state = crtc_state->base.state;
 
-	for_each_connector_in_state(state, connector, connector_state, i) {
+	for_each_new_connector_in_state(state, connector, connector_state, i) {
 		if (connector_state->crtc != crtc_state->base.crtc)
 			continue;
 
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index 578f7d20501f..937623ff6d7c 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -1239,8 +1239,6 @@ bool intel_ddi_is_audio_enabled(struct drm_i915_private *dev_priv,
 				 struct intel_crtc *intel_crtc);
 void intel_ddi_get_config(struct intel_encoder *encoder,
 			  struct intel_crtc_state *pipe_config);
-struct intel_encoder *
-intel_ddi_get_crtc_new_encoder(struct intel_crtc_state *crtc_state);
 
 void intel_ddi_init_dp_buf_reg(struct intel_encoder *encoder);
 void intel_ddi_clock_get(struct intel_encoder *encoder,
-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-09 14:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 14:52 [PATCH 0/5] drm/i915: Use new atomic iterator macros Maarten Lankhorst
2017-03-09 14:52 ` Maarten Lankhorst [this message]
2017-03-13  8:40   ` [PATCH 1/5] drm/i915: Use new atomic iterator macros in ddi Daniel Vetter
2017-03-09 14:52 ` [PATCH 2/5] drm/i915: Use new atomic iterator macros in fbc Maarten Lankhorst
2017-03-13 10:05   ` Daniel Vetter
2017-03-09 14:52 ` [PATCH 3/5] drm/i915: Use new atomic iterator macros in wm code Maarten Lankhorst
2017-03-13 10:07   ` Daniel Vetter
2017-03-09 14:52 ` [PATCH 4/5] drm/i915: Use new atomic iterator macros in display code Maarten Lankhorst
2017-03-13 10:15   ` Daniel Vetter
2017-03-13 11:08     ` Maarten Lankhorst
2017-03-14  6:50       ` Daniel Vetter
2017-03-15  8:23         ` Maarten Lankhorst
2017-03-16  8:47           ` Daniel Vetter
2017-07-19 11:58             ` Maarten Lankhorst
2017-03-09 14:52 ` [PATCH 5/5] drm/i915: Use new atomic iterator macros in cdclk Maarten Lankhorst
2017-03-13 10:15   ` Daniel Vetter
2017-03-09 18:18 ` ✓ Fi.CI.BAT: success for drm/i915: Use new atomic iterator macros Patchwork
2017-03-09 18:35 ` [PATCH 0/5] " Ville Syrjälä
2017-03-13 11:08   ` Maarten Lankhorst

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=1489071125-917-2-git-send-email-maarten.lankhorst@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@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