From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 3/4] fixup! drm/xe: Fix array of binds
Date: Mon, 2 Oct 2023 16:02:25 +0200 [thread overview]
Message-ID: <dbcc19c6-868f-b2df-fa0b-9c6ffe1501c9@linux.intel.com> (raw)
In-Reply-To: <20230929204637.1202492-4-rodrigo.vivi@intel.com>
On 9/29/23 22:44, Rodrigo Vivi wrote:
> ---
> drivers/gpu/drm/xe/xe_vm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 3a761608bb68..e90f59d6da55 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -3179,7 +3179,7 @@ static void vm_bind_ioctl_ops_unwind(struct xe_vm *vm,
> op->flags & XE_VMA_OP_NEXT_COMMITTED);
> }
>
> - drm_gpuva_ops_free(&vm->mgr, __ops);
> + drm_gpuva_ops_free(&vm->gpuvm, __ops);
> }
> }
>
next prev parent reply other threads:[~2023-10-02 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 20:44 [Intel-xe] [PATCH 0/4] Xe Core preparation for rebasing on drm-tip/drm-tip Rodrigo Vivi
2023-09-29 20:44 ` [Intel-xe] [PATCH 1/4] drm/gpuvm: rename struct drm_gpuva_manager to struct drm_gpuvm Rodrigo Vivi
2023-09-29 20:44 ` [Intel-xe] [PATCH 2/4] fixup! drm/xe: Port Xe to GPUVA Rodrigo Vivi
2023-10-02 14:01 ` Thomas Hellström
2023-09-29 20:44 ` [Intel-xe] [PATCH 3/4] fixup! drm/xe: Fix array of binds Rodrigo Vivi
2023-10-02 14:02 ` Thomas Hellström [this message]
2023-09-29 20:44 ` [Intel-xe] [PATCH 4/4] fixup! drm/xe: Rework xe_exec and the VM rebind worker to use the drm_exec helper Rodrigo Vivi
2023-10-02 14:03 ` Thomas Hellström
2023-09-29 23:03 ` [Intel-xe] ✗ CI.Patch_applied: failure for Xe Core preparation for rebasing on drm-tip/drm-tip 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=dbcc19c6-868f-b2df-fa0b-9c6ffe1501c9@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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