dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@gmail.com, daniel@ffwll.ch,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	cai.huoqing@linux.dev
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH 14/14] drm: Remove Kconfig option for legacy support (CONFIG_DRM_LEGACY)
Date: Wed, 22 Nov 2023 13:09:43 +0100	[thread overview]
Message-ID: <20231122122449.11588-15-tzimmermann@suse.de> (raw)
In-Reply-To: <20231122122449.11588-1-tzimmermann@suse.de>

Remove CONFIG_DRM_LEGACY from Kconfig. Nothing depends on the option.

Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
---
 drivers/gpu/drm/Kconfig | 21 ---------------------
 1 file changed, 21 deletions(-)

diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index cdbc56e076498..5150c8699a8b5 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -407,27 +407,6 @@ config DRM_HYPERV
 
 	 If M is selected the module will be called hyperv_drm.
 
-# Keep legacy drivers last
-
-menuconfig DRM_LEGACY
-	bool "Enable legacy drivers (DANGEROUS)"
-	depends on DRM && MMU
-	help
-	  Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
-	  APIs to user-space, which can be used to circumvent access
-	  restrictions and other security measures. For backwards compatibility
-	  those drivers are still available, but their use is highly
-	  inadvisable and might harm your system.
-
-	  You are recommended to use the safe modeset-only drivers instead, and
-	  perform 3D emulation in user-space.
-
-	  Unless you have strong reasons to go rogue, say "N".
-
-if DRM_LEGACY
-# leave here to list legacy drivers
-endif # DRM_LEGACY
-
 config DRM_EXPORT_FOR_TESTS
 	bool
 
-- 
2.42.1


  parent reply	other threads:[~2023-11-22 12:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 12:09 [PATCH 00/14] drm: Remove infrastructure for user-space mode setting Thomas Zimmermann
2023-11-22 12:09 ` [PATCH 01/14] arch/powerpc: Remove legacy DRM drivers from default configs Thomas Zimmermann
2023-11-27 21:03   ` Alex Deucher
2023-11-28  7:19   ` Cai Huoqing
2023-11-22 12:09 ` [PATCH 02/14] drm: Fix TODO list mentioning non-KMS drivers Thomas Zimmermann
2023-11-27 21:02   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 03/14] drm: Include <drm/drm_auth.h> Thomas Zimmermann
2023-11-27 21:03   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 04/14] drm/i915: " Thomas Zimmermann
2023-11-22 18:14   ` Jani Nikula
2023-11-22 12:09 ` [PATCH 05/14] accel: " Thomas Zimmermann
2023-11-27 21:03   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 06/14] drm: Include <drm/drm_device.h> Thomas Zimmermann
2023-11-22 12:09 ` [PATCH 07/14] drm/radeon: Do not include <drm/drm_legacy.h> Thomas Zimmermann
2023-11-27 21:00   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 08/14] drm: Remove entry points for legacy ioctls Thomas Zimmermann
2023-11-27 21:04   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 09/14] drm: Remove the legacy DRM_IOCTL_MODESET_CTL ioctl Thomas Zimmermann
2023-11-27 21:05   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 10/14] drm: Remove support for legacy drivers Thomas Zimmermann
2023-11-27 21:05   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 11/14] drm: Remove locking for legacy ioctls and DRM_UNLOCKED Thomas Zimmermann
2023-11-27 21:05   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 12/14] drm: Remove source code for non-KMS drivers Thomas Zimmermann
2023-11-27 21:06   ` Alex Deucher
2023-11-22 12:09 ` [PATCH 13/14] char/agp: Remove frontend code Thomas Zimmermann
2023-11-27 21:07   ` Alex Deucher
2023-11-22 12:09 ` Thomas Zimmermann [this message]
2023-11-27 21:07   ` [PATCH 14/14] drm: Remove Kconfig option for legacy support (CONFIG_DRM_LEGACY) Alex Deucher
2023-12-01  8:39 ` [PATCH 00/14] drm: Remove infrastructure for user-space mode setting Thomas Zimmermann
2023-12-06  9:20 ` Thomas Zimmermann

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=20231122122449.11588-15-tzimmermann@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=cai.huoqing@linux.dev \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    /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