On Mon, Jul 31, 2017 at 11:13:43AM +0200, Thierry Reding wrote: > From: Thierry Reding <treding@xxxxxxxxxx> > > The kerneldoc for drm_atomic_crtc_needs_modeset() is outdated and no > longer reflects the actual code. Fix that up to remove confusion. > > Signed-off-by: Thierry Reding <treding@xxxxxxxxxx> Reviewed-by: Daniel Vetter <daniel.vetter@xxxxxxxx> Pls push to drm-misc-next. -Daniel > --- > include/drm/drm_atomic.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomic.h > index 7cd0f303f5a3..a7adbf57b886 100644 > --- a/include/drm/drm_atomic.h > +++ b/include/drm/drm_atomic.h > @@ -883,7 +883,7 @@ void drm_state_dump(struct drm_device *dev, struct drm_printer *p); > * > * 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 > -- > 2.13.3 > > _______________________________________________ > dri-devel mailing list > dri-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
