From: Francesco Valla <francesco@valla.it>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Jonathan Corbet <corbet@lwn.net>,
Jocelyn Falempe <jfalempe@redhat.com>,
Javier Martinez Canillas <javierm@redhat.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Mario Limonciello <mario.limonciello@amd.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org, linux-embedded@vger.kernel.org,
Francesco Valla <francesco@valla.it>
Subject: [PATCH RFC v2 3/3] drm: docs: remove bootsplash from TODO
Date: Tue, 06 Jan 2026 15:25:42 +0100 [thread overview]
Message-ID: <20260106-drm_client_splash-v2-3-6e86a7434b59@valla.it> (raw)
In-Reply-To: <20260106-drm_client_splash-v2-0-6e86a7434b59@valla.it>
Now that a splash client exists, remove the bootsplash task from the
TODO list for the DRM subsystem.
Signed-off-by: Francesco Valla <francesco@valla.it>
---
Documentation/gpu/todo.rst | 17 -----------------
1 file changed, 17 deletions(-)
diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
index 9013ced318cb97d6895752d4cfe21c94d0000973..e32b303cca26fa284f795e30dab18cf9e9496a9e 100644
--- a/Documentation/gpu/todo.rst
+++ b/Documentation/gpu/todo.rst
@@ -754,23 +754,6 @@ See drivers/gpu/drm/amd/display/TODO for tasks.
Contact: Harry Wentland, Alex Deucher
-Bootsplash
-==========
-
-There is support in place now for writing internal DRM clients making it
-possible to pick up the bootsplash work that was rejected because it was written
-for fbdev.
-
-- [v6,8/8] drm/client: Hack: Add bootsplash example
- https://patchwork.freedesktop.org/patch/306579/
-
-- [RFC PATCH v2 00/13] Kernel based bootsplash
- https://lore.kernel.org/r/20171213194755.3409-1-mstaudt@suse.de
-
-Contact: Sam Ravnborg
-
-Level: Advanced
-
Brightness handling on devices with multiple internal panels
============================================================
--
2.52.0
prev parent reply other threads:[~2026-01-06 14:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 14:25 [PATCH RFC v2 0/3] Add splash DRM client Francesco Valla
2026-01-06 14:25 ` [PATCH RFC v2 1/3] drm: client: add splash client Francesco Valla
2026-01-06 14:47 ` Geert Uytterhoeven
2026-01-06 20:22 ` Francesco Valla
2026-01-06 18:58 ` Mario Limonciello (AMD) (kernel.org)
2026-01-06 20:32 ` Francesco Valla
2026-01-06 20:46 ` Mario Limonciello (AMD) (kernel.org)
2026-01-07 2:40 ` Mario Limonciello (AMD) (kernel.org)
2026-01-07 22:28 ` Francesco Valla
2026-01-22 13:36 ` Maxime Ripard
2026-01-23 20:59 ` Francesco Valla
2026-01-06 14:25 ` [PATCH RFC v2 2/3] MAINTAINERS: add entry for DRM " Francesco Valla
2026-01-06 14:25 ` Francesco Valla [this message]
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=20260106-drm_client_splash-v2-3-6e86a7434b59@valla.it \
--to=francesco@valla.it \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=mripard@kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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