All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 1/2] fixup! drm/i915/display: Remaining changes to make xe compile
Date: Mon, 15 May 2023 17:00:17 +0300	[thread overview]
Message-ID: <87jzx9itji.fsf@intel.com> (raw)
In-Reply-To: <20230512074335.1293293-1-jani.nikula@intel.com>


Lucas, Rodrigo, r-b on these two?

Thanks,
Jani.


On Fri, 12 May 2023, Jani Nikula <jani.nikula@intel.com> wrote:
> The dependency on display/intel_display_reg_defs.h is removed by
> upstream commit 6e4e9fbd5ba0 ("drm/i915/gt: drop dependency on
> VLV_DISPLAY_BASE").
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/gt/intel_gt_regs.h | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
> index 7ae5fa5a8ff7..af80d2fe739b 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
> @@ -7,9 +7,7 @@
>  #define __INTEL_GT_REGS__
>  
>  #include "i915_reg_defs.h"
> -#ifdef I915
>  #include "display/intel_display_reg_defs.h"	/* VLV_DISPLAY_BASE */
> -#endif
>  
>  /*
>   * The perf control registers are technically multicast registers, but the

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2023-05-15 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  7:43 [Intel-xe] [PATCH 1/2] fixup! drm/i915/display: Remaining changes to make xe compile Jani Nikula
2023-05-12  7:43 ` [Intel-xe] [PATCH 2/2] drm/i915/gt: drop dependency on VLV_DISPLAY_BASE Jani Nikula
2023-05-12 10:57 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] fixup! drm/i915/display: Remaining changes to make xe compile Patchwork
2023-05-12 10:59 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-12 11:03 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-12 11:24 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-05-15 14:00 ` Jani Nikula [this message]
2023-05-15 14:41   ` [Intel-xe] [PATCH 1/2] " Rodrigo Vivi
2023-05-15 16:42     ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2023-05-31 15:18 [Intel-xe] [PATCH 0/2] drm/xe: Small cleanups to DPT code Maarten Lankhorst
2023-05-31 15:18 ` [Intel-xe] [PATCH 1/2] fixup! drm/i915/display: Remaining changes to make xe compile Maarten Lankhorst
2023-06-01  9:13   ` Jani Nikula
2023-08-14  8:37 Maarten Lankhorst

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=87jzx9itji.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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.