From: Thierry Reding <treding@nvidia.com>
Date: Mon, 31 Jul 2017 11:13:43 +0200
Subject: drm/atomic: Update comment to match the code
Git-commit: 96bf51df6a90fc62de973ba7a9762d4150f26b94
Patch-mainline: v4.14-rc1
References: FATE#326289 FATE#326079 FATE#326049 FATE#322398 FATE#326166

The kerneldoc for drm_atomic_crtc_needs_modeset() is outdated and no
longer reflects the actual code. Fix that up to remove confusion.

Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20170731091343.21363-1-thierry.reding@gmail.com

Acked-by: Petr Tesarik <ptesarik@suse.com>
---
 include/drm/drm_atomic.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/include/drm/drm_atomic.h
+++ b/include/drm/drm_atomic.h
@@ -883,7 +883,7 @@ void drm_state_dump(struct drm_device *d
  *
  * To give drivers flexibility &struct drm_crtc_state has 3 booleans to track
  * whether the state CRTC changed enough to need a full modeset cycle:
- * planes_changed, mode_changed and active_changed. This helper simply
+ * mode_changed, active_changed and connectors_changed. This helper simply
  * combines these three to compute the overall need for a modeset for @state.
  *
  * The atomic helper code sets these booleans, but drivers can and should