public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cai Huoqing <cai.huoqing@linux.dev>
To: tzimmermann@suse.de
Cc: Cai Huoqing <cai.huoqing@linux.dev>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Randy Dunlap <rdunlap@infradead.org>,
	Borislav Petkov <bp@suse.de>, Danilo Krummrich <dakr@redhat.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [RESEND PATCH linux-next v2 08/10] drm: Add comments to Kconfig
Date: Sat,  3 Dec 2022 18:22:59 +0800	[thread overview]
Message-ID: <20221203102502.3185-9-cai.huoqing@linux.dev> (raw)
In-Reply-To: <20221203102502.3185-1-cai.huoqing@linux.dev>

Add comments to avoid removing DRM_LEGACY config menu,
because DRM_LEGACY menu could list other legacy drivers.

Signed-off-by: Cai Huoqing <cai.huoqing@linux.dev>
---
 drivers/gpu/drm/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 96d73208995a..520633a1e706 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -391,7 +391,7 @@ menuconfig DRM_LEGACY
 	  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
-- 
2.25.1


  parent reply	other threads:[~2022-12-03 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 10:22 [RESEND PATCH linux-next v2 00/10] drm: Remove some obsolete drivers(tdfx, mga, i810, savage, r128, sis, via) Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 01/10] drm: Remove the obsolete driver-i810 Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 02/10] drm: Remove the obsolete driver-mga Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 03/10] drm: Remove the obsolete driver-r128 Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 04/10] drm: Remove the obsolete driver-savage Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 05/10] drm: Remove the obsolete driver-sis Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 06/10] drm: Remove the obsolete driver-tdfx Cai Huoqing
2022-12-03 10:22 ` [RESEND PATCH linux-next v2 07/10] drm: Remove the obsolete driver-via Cai Huoqing
2022-12-03 10:22 ` Cai Huoqing [this message]
2022-12-03 10:23 ` [RESEND PATCH linux-next v2 09/10] drm: Remove some obsolete drm pciids(tdfx, mga, i810, savage, r128, sis, via) Cai Huoqing
2022-12-03 10:23 ` [RESEND PATCH linux-next v2 10/10] MAINTAINERS: Remove some obsolete drivers info(tdfx, mga, i810, savage, r128, sis) Cai Huoqing
2022-12-08 12:42 ` [RESEND PATCH linux-next v2 00/10] drm: Remove some obsolete drivers(tdfx, mga, i810, savage, r128, sis, via) Cai Huoqing
2023-01-05 12:40   ` Daniel Vetter
2023-01-05 13:01     ` Thomas Zimmermann
2023-01-12  9:44       ` Daniel Vetter
2023-01-13  9:31 ` 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=20221203102502.3185-9-cai.huoqing@linux.dev \
    --to=cai.huoqing@linux.dev \
    --cc=airlied@gmail.com \
    --cc=bp@suse.de \
    --cc=dakr@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sam@ravnborg.org \
    --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