All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dg1: remove __maybe_unused leftover
Date: Fri, 20 Aug 2021 10:35:55 +0200	[thread overview]
Message-ID: <23c01761-bfd3-ff98-b549-f0bf02953e15@linux.intel.com> (raw)
In-Reply-To: <20210819210349.95103-1-lucas.demarchi@intel.com>

Op 19-08-2021 om 23:03 schreef Lucas De Marchi:
> This was added in commit 05e265841f7e ("drm/i915/dg1: add initial DG-1
> definitions") so we could continue to add support for DG1 without
> risk to expose a broken UAPI. Now that we added DG1 to the PCI ID list
> i915 may bind to, remove the leftover.
>
> Fixes: d5ef86b38e4c ("drm/i915: Add pci ids and uapi for DG1")
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 93ccdc6bbd03..96cfd6427cec 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -894,7 +894,7 @@ static const struct intel_device_info rkl_info = {
>  	.has_snoop = 1, \
>  	.is_dgfx = 1
>  
> -static const struct intel_device_info dg1_info __maybe_unused = {
> +static const struct intel_device_info dg1_info = {
>  	GEN12_FEATURES,
>  	DGFX_FEATURES,
>  	.graphics_rel = 10,

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>


      parent reply	other threads:[~2021-08-20  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 21:03 [Intel-gfx] [PATCH] drm/i915/dg1: remove __maybe_unused leftover Lucas De Marchi
2021-08-19 21:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-08-19 23:26 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-08-20  8:35 ` Maarten Lankhorst [this message]

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=23c01761-bfd3-ff98-b549-f0bf02953e15@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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.