From: Jerry Zhang <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: fix duplicated code
Date: Tue, 21 Mar 2017 10:34:07 +0800 [thread overview]
Message-ID: <58D0911F.9070601@amd.com> (raw)
In-Reply-To: <1490062243-547-1-git-send-email-David1.Zhou-5C7GfCeVMHo@public.gmane.org>
On 03/21/2017 10:10 AM, Chunming Zhou wrote:
> it could come from branch merge.
>
> Change-Id: I16959aad6ca6d64cb8330f23ee6472eec4cf2a3e
> Signed-off-by: Chunming Zhou <David1.Zhou@amd.com>
Reviewed-by: Junwei Zhang <Jerry.Zhang@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> index 81c3c75..dd7df45 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> @@ -990,10 +990,6 @@ static int amdgpu_vm_bo_update_mapping(struct amdgpu_device *adev,
>
> ring = container_of(vm->entity.sched, struct amdgpu_ring, sched);
>
> - memset(¶ms, 0, sizeof(params));
> - params.adev = adev;
> - params.src = src;
> -
> /* sync to everything on unmapping */
> if (!(flags & AMDGPU_PTE_VALID))
> owner = AMDGPU_FENCE_OWNER_UNDEFINED;
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-03-21 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 2:10 [PATCH] drm/amdgpu: fix duplicated code Chunming Zhou
[not found] ` <1490062243-547-1-git-send-email-David1.Zhou-5C7GfCeVMHo@public.gmane.org>
2017-03-21 2:34 ` Jerry Zhang [this message]
[not found] ` <58D0911F.9070601-5C7GfCeVMHo@public.gmane.org>
2017-03-21 6:37 ` Christian König
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=58D0911F.9070601@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.