From: Andi Shyti <andi.shyti@linux.intel.com>
To: Chris Wilson <chris.p.wilson@linux.intel.com>,
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 4/4] drm/i915: Remove unnecessary include
Date: Tue, 1 Aug 2023 16:19:55 +0200 [thread overview]
Message-ID: <20230801141955.383305-5-andi.shyti@linux.intel.com> (raw)
In-Reply-To: <20230801141955.383305-1-andi.shyti@linux.intel.com>
The inclusion of intel_gt_defines.h was initially added to
i915_drv.h to provide the definition of I915_MAX_GT, where it was
originally defined.
However, since I915_MAX_GT is now included in
i915_gem_object_types.h, it sis no longer required in i915_drv.h.
Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Chris Wilson <chris.p.wilson@linux.intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 1584b01e1bd6c..a1a2fe31f4340 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -44,7 +44,6 @@
#include "gem/i915_gem_stolen.h"
#include "gt/intel_engine.h"
-#include "gt/intel_gt_defines.h"
#include "gt/intel_gt_types.h"
#include "gt/intel_region_lmem.h"
#include "gt/intel_workarounds.h"
--
2.40.1
next prev parent reply other threads:[~2023-08-01 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 14:19 [Intel-gfx] [PATCH 0/4] Invalidate TLB cache for all GT's Andi Shyti
2023-08-01 14:19 ` [Intel-gfx] [PATCH 1/4] drm/i915/gt: Move TLB invalidation to its own file Andi Shyti
2023-08-01 14:19 ` [Intel-gfx] [PATCH 2/4] i915/drm/gt: Move the gt defines in the gt directory Andi Shyti
2023-08-01 14:19 ` [Intel-gfx] [PATCH 3/4] drm/i915: Invalidate the TLBs on each GT Andi Shyti
2023-08-01 14:19 ` Andi Shyti [this message]
2023-08-01 14:40 ` [Intel-gfx] [PATCH 0/4] Invalidate TLB cache for all GT's Mauro Carvalho Chehab
2023-08-01 16:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-08-01 16:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-01 17:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-01 21:57 ` [Intel-gfx] ✓ 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=20230801141955.383305-5-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mauro.chehab@linux.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