From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH v3 3/3] drm/xe/userptr: remove tmp_evict list
Date: Fri, 21 Feb 2025 14:38:43 +0000 [thread overview]
Message-ID: <20250221143840.167150-6-matthew.auld@intel.com> (raw)
In-Reply-To: <20250221143840.167150-4-matthew.auld@intel.com>
Doesn't look to be used.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: 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 0118a1147668..996000f2424e 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -660,7 +660,6 @@ int xe_vm_userptr_pin(struct xe_vm *vm)
{
struct xe_userptr_vma *uvma, *next;
int err = 0;
- LIST_HEAD(tmp_evict);
xe_assert(vm->xe, !xe_vm_in_fault_mode(vm));
lockdep_assert_held_write(&vm->lock);
--
2.48.1
next prev parent reply other threads:[~2025-02-21 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 14:38 [PATCH v3 1/3] drm/xe/userptr: restore invalidation list on error Matthew Auld
2025-02-21 14:38 ` [PATCH v3 2/3] drm/xe/userptr: fix EFAULT handling Matthew Auld
2025-02-21 14:38 ` Matthew Auld [this message]
2025-02-21 15:39 ` ✓ CI.Patch_applied: success for series starting with [v3,1/3] drm/xe/userptr: restore invalidation list on error Patchwork
2025-02-21 15:39 ` ✓ CI.checkpatch: " Patchwork
2025-02-21 15:40 ` ✓ CI.KUnit: " Patchwork
2025-02-21 15:57 ` ✓ CI.Build: " Patchwork
2025-02-21 15:59 ` ✓ CI.Hooks: " Patchwork
2025-02-21 16:01 ` ✓ CI.checksparse: " Patchwork
2025-02-21 16:28 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-21 17:41 ` [PATCH v3 1/3] " Matthew Brost
2025-02-22 5:26 ` ✓ Xe.CI.Full: success for series starting with [v3,1/3] " 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=20250221143840.167150-6-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=thomas.hellstrom@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