All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	rodrigo.vivi@intel.com, lucas.demarchi@intel.com
Subject: Re: [PATCH 03/10] drm/i915/display: include i915_gpu_error.h where needed
Date: Fri, 31 May 2024 14:35:27 +0300	[thread overview]
Message-ID: <Zlm1__e57Bt11mAM@intel.com> (raw)
In-Reply-To: <a5dbb8d46403761bd8518db45fa71dc55930d3cf.1717004739.git.jani.nikula@intel.com>

On Wed, May 29, 2024 at 08:48:07PM +0300, Jani Nikula wrote:
> Include what you use. With this, we can drop the include from xe compat
> i915_drv.h.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dmc.c          | 1 +
>  drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h | 1 -
>  2 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c b/drivers/gpu/drm/i915/display/intel_dmc.c
> index 63fccdda56c0..b5ebb0f5b269 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc.c
> +++ b/drivers/gpu/drm/i915/display/intel_dmc.c
> @@ -26,6 +26,7 @@
>  #include <linux/firmware.h>
>  
>  #include "i915_drv.h"
> +#include "i915_gpu_error.h"

Someone should probably convert intel_dmc_print_error_state()
to use the drm_printer interface instead, assuming that is the
only thing that needs this header in intel_dmc.c.

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2024-05-31 11:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 17:48 [PATCH 00/10] drm/i915 and drm/xe display and compat cleanups Jani Nikula
2024-05-29 17:48 ` [PATCH 01/10] drm/i915/display: include gem/i915_gem_stolen.h where needed Jani Nikula
2024-05-31 11:03   ` Rodrigo Vivi
2024-05-31 12:03     ` Jani Nikula
2024-06-04 11:41       ` Jani Nikula
2024-06-04 20:34         ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 02/10] drm/i915/display: include gt/intel_gt_types.h " Jani Nikula
2024-05-31 11:05   ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 03/10] drm/i915/display: include i915_gpu_error.h " Jani Nikula
2024-05-31 11:07   ` Rodrigo Vivi
2024-05-31 11:35   ` Ville Syrjälä [this message]
2024-05-31 12:07     ` Jani Nikula
2024-05-31 12:17       ` Jani Nikula
2024-05-29 17:48 ` [PATCH 04/10] drm/i915/display: include intel_uncore.h " Jani Nikula
2024-05-31 11:07   ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 05/10] drm/i915/display: include intel_step.h " Jani Nikula
2024-05-31 12:03   ` Rodrigo Vivi
2024-05-31 12:08     ` Jani Nikula
2024-05-29 17:48 ` [PATCH 06/10] drm/i915/display: include xe_bo.h, gem_object_types etc. " Jani Nikula
2024-05-31 12:07   ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 07/10] drm/xe/display: move compat uncore stubs to the correct file Jani Nikula
2024-05-31 12:08   ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 08/10] drm/xe/display: move compat runtime pm " Jani Nikula
2024-05-31 12:09   ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 09/10] drm/xe/display: reduce includes in compat i915_drv.h Jani Nikula
2024-05-31 12:09   ` Rodrigo Vivi
2024-05-29 17:48 ` [PATCH 10/10] drm/xe/display: drop i915_drv.h include from xe code Jani Nikula
2024-05-31 12:10   ` Rodrigo Vivi
2024-05-29 18:26 ` ✓ CI.Patch_applied: success for drm/i915 and drm/xe display and compat cleanups Patchwork
2024-05-29 18:26 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-29 18:27 ` ✓ CI.KUnit: success " Patchwork
2024-05-29 18:39 ` ✓ CI.Build: " Patchwork
2024-05-29 18:39 ` ✗ CI.Hooks: failure " Patchwork
2024-05-29 18:41 ` ✗ CI.checksparse: warning " Patchwork
2024-05-29 18:48 ` ✗ Fi.CI.CHECKPATCH: " Patchwork
2024-05-29 18:48 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-05-29 18:56 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-29 19:20 ` ✓ CI.BAT: " Patchwork
2024-05-29 21:57 ` ✗ CI.FULL: failure " Patchwork
2024-05-30 19:38 ` ✗ Fi.CI.IGT: " 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=Zlm1__e57Bt11mAM@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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.