From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Tejas Upadhyay <tejas.upadhyay@intel.com>
Subject: [PATCH v2 4/4] drm/xe: Drop unnecessary include from xe_tile.h
Date: Tue, 3 Feb 2026 22:12:39 +0100 [thread overview]
Message-ID: <20260203211240.745-5-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20260203211240.745-1-michal.wajdeczko@intel.com>
We don't need to include xe_device_types.h there.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
---
v1: https://patchwork.freedesktop.org/patch/656887/?series=149807&rev=1
v2: rebased
---
drivers/gpu/drm/xe/xe_tile.h | 4 ++--
drivers/gpu/drm/xe/xe_tile_sysfs.c | 2 +-
drivers/gpu/drm/xe/xe_vram_freq.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_tile.h b/drivers/gpu/drm/xe/xe_tile.h
index 734132eddda5..a2a2c0e936b8 100644
--- a/drivers/gpu/drm/xe/xe_tile.h
+++ b/drivers/gpu/drm/xe/xe_tile.h
@@ -6,10 +6,10 @@
#ifndef _XE_TILE_H_
#define _XE_TILE_H_
-#include "xe_device_types.h"
+#include "xe_tile_types.h"
+struct xe_device;
struct xe_pagemap;
-struct xe_tile;
int xe_tile_init_early(struct xe_tile *tile, struct xe_device *xe, u8 id);
int xe_tile_init_noalloc(struct xe_tile *tile);
diff --git a/drivers/gpu/drm/xe/xe_tile_sysfs.c b/drivers/gpu/drm/xe/xe_tile_sysfs.c
index 9e1236a9ec67..f2bf7314954d 100644
--- a/drivers/gpu/drm/xe/xe_tile_sysfs.c
+++ b/drivers/gpu/drm/xe/xe_tile_sysfs.c
@@ -7,8 +7,8 @@
#include <linux/sysfs.h>
#include <drm/drm_managed.h>
+#include "xe_device_types.h"
#include "xe_pm.h"
-#include "xe_tile.h"
#include "xe_tile_sysfs.h"
#include "xe_vram_freq.h"
diff --git a/drivers/gpu/drm/xe/xe_vram_freq.c b/drivers/gpu/drm/xe/xe_vram_freq.c
index 6f8281e0b96a..8717367ccd4c 100644
--- a/drivers/gpu/drm/xe/xe_vram_freq.c
+++ b/drivers/gpu/drm/xe/xe_vram_freq.c
@@ -5,9 +5,9 @@
#include <linux/sysfs.h>
#include <drm/drm_managed.h>
+#include "xe_device_types.h"
#include "xe_pcode.h"
#include "xe_pcode_api.h"
-#include "xe_tile.h"
#include "xe_tile_sysfs.h"
#include "xe_vram_freq.h"
--
2.47.1
next prev parent reply other threads:[~2026-02-03 21:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 21:12 [PATCH v2 0/4] Some more _types.h cleanups Michal Wajdeczko
2026-02-03 21:12 ` [PATCH v2 1/4] drm/xe: Move xe_root_tile_mmio() to xe_device.h Michal Wajdeczko
2026-02-03 21:12 ` [PATCH v2 2/4] drm/xe: Promote struct xe_mmio definition to own file Michal Wajdeczko
2026-02-03 21:12 ` [PATCH v2 3/4] drm/xe: Promote struct xe_tile " Michal Wajdeczko
2026-02-03 23:47 ` Matt Roper
2026-02-03 21:12 ` Michal Wajdeczko [this message]
2026-02-03 21:52 ` ✗ CI.checkpatch: warning for Some more _types.h cleanups (rev3) Patchwork
2026-02-03 21:53 ` ✓ CI.KUnit: success " Patchwork
2026-02-03 22:26 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-02-04 12:36 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-04 23:29 ` ✗ CI.checkpatch: warning for Some more _types.h cleanups (rev4) Patchwork
2026-02-04 23:31 ` ✓ CI.KUnit: success " Patchwork
2026-02-05 0:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-05 14:27 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-05 20:07 ` Michal Wajdeczko
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=20260203211240.745-5-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=tejas.upadhyay@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