From: Matthew Brost <matthew.brost@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-xe@lists.freedesktop.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH 2/2] drm/xe/userptr: remove tmp_evict list
Date: Thu, 13 Feb 2025 11:42:34 -0800 [thread overview]
Message-ID: <Z65LKme2r8dgmfxc@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250213135808.189144-4-matthew.auld@intel.com>
On Thu, Feb 13, 2025 at 01:58:10PM +0000, Matthew Auld wrote:
> Doesn't look to be used.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.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 1caee9cbeafb..2d8f99c7c3a9 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-13 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 13:58 [PATCH 1/2] drm/xe/userptr: fix EFAULT handling Matthew Auld
2025-02-13 13:58 ` [PATCH 2/2] drm/xe/userptr: remove tmp_evict list Matthew Auld
2025-02-13 19:42 ` Matthew Brost [this message]
2025-02-13 15:05 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/userptr: fix EFAULT handling Patchwork
2025-02-13 15:06 ` ✓ CI.checkpatch: " Patchwork
2025-02-13 15:07 ` ✓ CI.KUnit: " Patchwork
2025-02-13 15:24 ` ✓ CI.Build: " Patchwork
2025-02-13 15:26 ` ✓ CI.Hooks: " Patchwork
2025-02-13 15:27 ` ✓ CI.checksparse: " Patchwork
2025-02-13 15:48 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-14 8:46 ` ✗ Xe.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=Z65LKme2r8dgmfxc@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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