Intel-XE Archive on 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>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/ltphy: include intel_display_utils.h instead of i915_utils.h
Date: Wed, 12 Nov 2025 14:38:13 -0500	[thread overview]
Message-ID: <aRTiJdbO8fnW8cIv@intel.com> (raw)
In-Reply-To: <20251112181342.107911-1-jani.nikula@intel.com>

On Wed, Nov 12, 2025 at 08:13:42PM +0200, Jani Nikula wrote:
> Display code stopped using i915_utils.h in favour of
> intel_display_utils.h. Fix recent additions.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>

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

> ---
>  drivers/gpu/drm/i915/display/intel_lt_phy.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_lt_phy.c b/drivers/gpu/drm/i915/display/intel_lt_phy.c
> index bebd7488aab9..a67eb4f7f897 100644
> --- a/drivers/gpu/drm/i915/display/intel_lt_phy.c
> +++ b/drivers/gpu/drm/i915/display/intel_lt_phy.c
> @@ -6,7 +6,6 @@
>  #include <drm/drm_print.h>
>  
>  #include "i915_reg.h"
> -#include "i915_utils.h"
>  #include "intel_cx0_phy.h"
>  #include "intel_cx0_phy_regs.h"
>  #include "intel_ddi.h"
> @@ -14,6 +13,7 @@
>  #include "intel_de.h"
>  #include "intel_display.h"
>  #include "intel_display_types.h"
> +#include "intel_display_utils.h"
>  #include "intel_dpll_mgr.h"
>  #include "intel_hdmi.h"
>  #include "intel_lt_phy.h"
> -- 
> 2.47.3
> 

  parent reply	other threads:[~2025-11-12 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 18:13 [PATCH] drm/i915/ltphy: include intel_display_utils.h instead of i915_utils.h Jani Nikula
2025-11-12 19:07 ` ✓ CI.KUnit: success for " Patchwork
2025-11-12 19:38 ` Rodrigo Vivi [this message]
2025-11-13  8:41   ` [PATCH] " Jani Nikula
2025-11-12 19:46 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-11-13  2:21 ` ✓ Xe.CI.Full: " 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=aRTiJdbO8fnW8cIv@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox