From: Maxime Ripard Date: Mon, 27 Apr 2026 07:02:58 +0000 (+0200) Subject: Documentation: drm: Remove drm_atomic_state rename entry X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d85dfb495f3c5f0666bc5464b7cb7d5f0d27f5be;p=thirdparty%2Fkernel%2Flinux.git Documentation: drm: Remove drm_atomic_state rename entry We just did that item so we can remove it. Reviewed-by: Luca Ceresoli Acked-by: Jani Nikula Signed-off-by: Maxime Ripard Signed-off-by: Dave Airlie Link: https://patch.msgid.link/20260427-drm-drm-atomic-update-v4-2-c0e713bfdf25@kernel.org --- diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst index 2ceb00e08c59f..cdddf8db35f53 100644 --- a/Documentation/gpu/todo.rst +++ b/Documentation/gpu/todo.rst @@ -152,29 +152,6 @@ Contact: Simona Vetter, respective driver maintainers Level: Advanced -Rename drm_atomic_commit ------------------------ - -The KMS framework uses two slightly different definitions for the ``state`` -concept. For a given object (plane, CRTC, encoder, etc., so -``drm_$OBJECT_state``), the state is the entire state of that object. However, -at the device level, ``drm_atomic_commit`` refers to a state update for a -limited number of objects. - -The state isn't the entire device state, but only the full state of some -objects in that device. This is confusing to newcomers, and -``drm_atomic_commit`` should be renamed to something clearer like -``drm_atomic_commit``. - -In addition to renaming the structure itself, it would also imply renaming some -related functions (``drm_atomic_commit_alloc``, ``drm_atomic_commit_get``, -``drm_atomic_commit_put``, ``drm_atomic_commit_init``, -``__drm_atomic_commit_free``, etc.). - -Contact: Maxime Ripard - -Level: Advanced - Fallout from atomic KMS -----------------------