All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Eero Tamminen <eero.t.tamminen@intel.com>
Subject: Re: [PATCH] drm/xe: display support should not depend on EXPERT
Date: Thu, 11 Jan 2024 12:48:22 +0200	[thread overview]
Message-ID: <87wmsgtabt.fsf@intel.com> (raw)
In-Reply-To: <20240111104716.3548744-1-jani.nikula@intel.com>

On Thu, 11 Jan 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> Remove the DRM_XE_DISPLAY config dependency on EXPERT. I can only
> presume the idea was only experts should be able to disable it, but the
> effect is the opposite.

Forgot to add,

Reported-by: Eero Tamminen <eero.t.tamminen@intel.com>

> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/xe/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
> index 1cced50d8d8c..e36ae1f0d885 100644
> --- a/drivers/gpu/drm/xe/Kconfig
> +++ b/drivers/gpu/drm/xe/Kconfig
> @@ -47,7 +47,7 @@ config DRM_XE
>  
>  config DRM_XE_DISPLAY
>  	bool "Enable display support"
> -	depends on DRM_XE && EXPERT && DRM_XE=m
> +	depends on DRM_XE && DRM_XE=m
>  	select FB_IOMEM_HELPERS
>  	select I2C
>  	select I2C_ALGOBIT

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-01-11 10:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 10:47 [PATCH] drm/xe: display support should not depend on EXPERT Jani Nikula
2024-01-11 10:48 ` Jani Nikula [this message]
2024-01-11 10:58   ` Francois Dugast
2024-01-15  7:33     ` Jani Nikula
2024-01-11 11:21 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-11 11:22 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-11 11:29   ` Jani Nikula
2024-01-11 11:23 ` ✓ CI.KUnit: success " Patchwork
2024-01-11 11:30 ` ✓ CI.Build: " Patchwork
2024-01-11 11:31 ` ✓ CI.Hooks: " Patchwork
2024-01-11 11:32 ` ✓ CI.checksparse: " Patchwork
2024-01-11 12:07 ` ✓ CI.BAT: " 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=87wmsgtabt.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=eero.t.tamminen@intel.com \
    --cc=intel-xe@lists.freedesktop.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 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.