Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [Intel-xe] [PATCH v6 5/6] drm/xe: Remove __xe_vm_bind forward declaration
Date: Fri,  7 Jul 2023 23:56:13 -0700	[thread overview]
Message-ID: <20230708065614.1754600-6-matthew.brost@intel.com> (raw)
In-Reply-To: <20230708065614.1754600-1-matthew.brost@intel.com>

Not needed so remove it.

Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
 drivers/gpu/drm/xe/xe_vm.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index ccc4c870260c..23619ea873ac 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -696,11 +696,6 @@ static void preempt_rebind_work_func(struct work_struct *w)
 	trace_xe_vm_rebind_worker_exit(vm);
 }
 
-struct async_op_fence;
-static int __xe_vm_bind(struct xe_vm *vm, struct xe_vma *vma,
-			struct xe_engine *e, struct xe_sync_entry *syncs,
-			u32 num_syncs, struct async_op_fence *afence);
-
 static bool vma_userptr_invalidate(struct mmu_interval_notifier *mni,
 				   const struct mmu_notifier_range *range,
 				   unsigned long cur_seq)
-- 
2.34.1


  parent reply	other threads:[~2023-07-08  6:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  6:56 [Intel-xe] [PATCH v6 0/6] GPUVA with no uAPI changes Matthew Brost
2023-07-08  6:56 ` [Intel-xe] [PATCH v6 1/6] drm/xe: Ban a VM if rebind worker hits an error Matthew Brost
2023-07-08  6:56 ` [Intel-xe] [PATCH v6 2/6] drm/xe: Add helpers to hide struct xe_vma internals Matthew Brost
2023-07-08  6:56 ` [Intel-xe] [PATCH v6 3/6] drm: manager to keep track of GPUs VA mappings Matthew Brost
2023-07-08  6:56 ` [Intel-xe] [PATCH v6 4/6] drm: debugfs: provide infrastructure to dump a DRM GPU VA space Matthew Brost
2023-07-08  6:56 ` Matthew Brost [this message]
2023-07-08  6:56 ` [Intel-xe] [PATCH v6 6/6] drm/xe: Port Xe to GPUVA Matthew Brost
2023-07-08  6:58 ` [Intel-xe] ✓ CI.Patch_applied: success for GPUVA with no uAPI changes Patchwork
2023-07-08  6:59 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-08  7:00 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-08  7:04 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-08  7:04 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-08  7:05 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-07-08  7:51 ` [Intel-xe] ○ CI.BAT: info " 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=20230708065614.1754600-6-matthew.brost@intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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