All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: remove unused config DRM_I915_UNSTABLE
Date: Mon, 27 Mar 2023 10:54:08 -0400	[thread overview]
Message-ID: <ZCGuEPfP3VDcdHou@intel.com> (raw)
In-Reply-To: <20230327105330.312131-2-jani.nikula@intel.com>

On Mon, Mar 27, 2023 at 01:53:30PM +0300, Jani Nikula wrote:
> Essentially this is a revert of commit d9d54a530a70 ("drm/i915: Put
> future HW and their uAPIs under STAGING & BROKEN").
> 
> We currently have no users for this config option. The last one was
> removed in 8c26491f5853 ("drm/i915: Kill the fake lmem support"). Drop
> it altogether; it's easy enough to resurrect if need arises.
> 
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/i915/Kconfig          |  6 ------
>  drivers/gpu/drm/i915/Kconfig.unstable | 21 ---------------------
>  2 files changed, 27 deletions(-)
>  delete mode 100644 drivers/gpu/drm/i915/Kconfig.unstable
> 
> diff --git a/drivers/gpu/drm/i915/Kconfig b/drivers/gpu/drm/i915/Kconfig
> index 98f4e44976e0..06a0ca157e89 100644
> --- a/drivers/gpu/drm/i915/Kconfig
> +++ b/drivers/gpu/drm/i915/Kconfig
> @@ -164,11 +164,5 @@ menu "drm/i915 Profile Guided Optimisation"
>  	source "drivers/gpu/drm/i915/Kconfig.profile"
>  endmenu
>  
> -menu "drm/i915 Unstable Evolution"
> -	visible if EXPERT && STAGING && BROKEN
> -	depends on DRM_I915
> -	source "drivers/gpu/drm/i915/Kconfig.unstable"
> -endmenu
> -
>  config DRM_I915_GVT
>  	bool
> diff --git a/drivers/gpu/drm/i915/Kconfig.unstable b/drivers/gpu/drm/i915/Kconfig.unstable
> deleted file mode 100644
> index cf151a297ed7..000000000000
> --- a/drivers/gpu/drm/i915/Kconfig.unstable
> +++ /dev/null
> @@ -1,21 +0,0 @@
> -# SPDX-License-Identifier: GPL-2.0-only
> -config DRM_I915_UNSTABLE
> -	bool "Enable unstable API for early prototype development"
> -	depends on EXPERT
> -	depends on STAGING
> -	depends on BROKEN # should never be enabled by distros!
> -	# We use the dependency on !COMPILE_TEST to not be enabled in
> -	# allmodconfig or allyesconfig configurations
> -	depends on !COMPILE_TEST
> -	default n
> -	help
> -	  Enable prototype uAPI under general discussion before they are
> -	  finalized. Such prototypes may be withdrawn or substantially
> -	  changed before release. They are only enabled here so that a wide
> -	  number of interested parties (userspace driver developers) can
> -	  verify that the uAPI meet their expectations. These uAPI should
> -	  never be used in production.
> -
> -	  Recommended for driver developers _only_.
> -
> -	  If in the slightest bit of doubt, say "N".
> -- 
> 2.39.2
> 

  reply	other threads:[~2023-03-27 14:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 10:53 [Intel-gfx] [PATCH 1/2] [core-for-CI] Revert "Revert "drm/i915: Don't select BROKEN"" Jani Nikula
2023-03-27 10:53 ` [Intel-gfx] [PATCH 2/2] drm/i915: remove unused config DRM_I915_UNSTABLE Jani Nikula
2023-03-27 14:54   ` Rodrigo Vivi [this message]
2023-03-28 15:46     ` Jani Nikula
2023-03-27 12:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2,core-for-CI] Revert "Revert "drm/i915: Don't select BROKEN"" Patchwork
2023-03-27 12:44 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-03-27 14:54 ` [Intel-gfx] [PATCH 1/2] [core-for-CI] " Rodrigo Vivi
2023-03-27 19:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2,core-for-CI] Revert "Revert "drm/i915: Don't select BROKEN"" (rev2) Patchwork
2023-03-27 19:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-03-28  2:43 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

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=ZCGuEPfP3VDcdHou@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.