From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH 3/3] drm/xe/vm: don't include xe_gt.h
Date: Fri, 12 Apr 2024 12:31:47 +0100 [thread overview]
Message-ID: <20240412113144.259426-6-matthew.auld@intel.com> (raw)
In-Reply-To: <20240412113144.259426-4-matthew.auld@intel.com>
clangd complains here, since nothing in xe_gt.h seems to be needed.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/xe/xe_vm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index 300d166f412e..35b63512d288 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -27,7 +27,6 @@
#include "xe_device.h"
#include "xe_drm_client.h"
#include "xe_exec_queue.h"
-#include "xe_gt.h"
#include "xe_gt_pagefault.h"
#include "xe_gt_tlb_invalidation.h"
#include "xe_migrate.h"
--
2.44.0
next prev parent reply other threads:[~2024-04-12 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 11:31 [PATCH 1/3] drm/xe/vm: prevent UAF with asid based lookup Matthew Auld
2024-04-12 11:31 ` [PATCH 2/3] drm/xe/vm: drop vm->destroy_work Matthew Auld
2024-04-12 22:32 ` Matthew Brost
2024-04-12 11:31 ` Matthew Auld [this message]
2024-04-12 22:34 ` [PATCH 3/3] drm/xe/vm: don't include xe_gt.h Matthew Brost
2024-04-12 14:06 ` [PATCH 1/3] drm/xe/vm: prevent UAF with asid based lookup Lucas De Marchi
2024-04-12 14:42 ` Matthew Auld
2024-04-12 22:26 ` Matthew Brost
2024-04-15 8:48 ` ✓ CI.Patch_applied: success for series starting with [1/3] " Patchwork
2024-04-15 8:48 ` ✓ CI.checkpatch: " Patchwork
2024-04-15 8:49 ` ✓ CI.KUnit: " Patchwork
2024-04-15 9:08 ` ✓ CI.Build: " Patchwork
2024-04-15 9:11 ` ✓ CI.Hooks: " Patchwork
2024-04-15 9:12 ` ✓ CI.checksparse: " Patchwork
2024-04-15 9:51 ` ✓ CI.BAT: " Patchwork
2024-04-15 13:13 ` ✗ CI.FULL: failure " 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=20240412113144.259426-6-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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