linux-kernel - [PATCH] fbdev/ todo: Remove obsolete line about VGA16fb memory region

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20251115175955.203312-1-hsukrut3@gmail.com>
Date: Sat, 15 Nov 2025 23:29:54 +0530
From: Sukrut Heroorkar <hsukrut3@...il.com>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	Maxime Ripard <mripard@...nel.org>,
	Thomas Zimmermann <tzimmermann@...e.de>,
	David Airlie <airlied@...il.com>,
	Simona Vetter <simona@...ll.ch>,
	Jonathan Corbet <corbet@....net>,
	dri-devel@...ts.freedesktop.org (open list:DRM DRIVERS),
	linux-doc@...r.kernel.org (open list:DOCUMENTATION),
	linux-kernel@...r.kernel.org (open list)
Cc: shuah@...nel.org,
	david.hunter.linux@...il.com,
	Sukrut Heroorkar <hsukrut3@...il.com>
Subject: [PATCH] fbdev/ todo: Remove obsolete line about VGA16fb memory region

The fbdev TODO item  mentions that VGA16fb does not request its memory
region properly. This was fixed by commit 0be42724bf4d ("fbdev: vga16fb:
Request memory region"). Remove the obsolete line.

Signed-off-by: Sukrut Heroorkar <hsukrut3@...il.com>
---
 Documentation/gpu/todo.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
index 9013ced318cb..277b3e495726 100644
--- a/Documentation/gpu/todo.rst
+++ b/Documentation/gpu/todo.rst
@@ -424,8 +424,7 @@ Go through these drivers and add code to request the memory regions
 that the driver uses. This requires adding calls to request_mem_region(),
 pci_request_region() or similar functions. Use helpers for managed cleanup
 where possible. Problematic areas include hardware that has exclusive ranges
-like VGA. VGA16fb does not request the range as it is expected.
-Drivers are pretty bad at doing this and there used to be conflicts among
+like VGA. Drivers are pretty bad at doing this and there used to be conflicts among
 DRM and fbdev drivers. Still, it's the correct thing to do.
 
 Contact: Thomas Zimmermann <tzimmermann@...e.de>
-- 
2.43.0