All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yadav, Arvind" <arvyadav@amd.com>
To: Prike Liang <Prike.Liang@amd.com>
Cc: Alexander.Deucher@amd.com, Christian.Koenig@amd.com,
	amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/amdgpu: set the evf name to identify the userq case
Date: Tue, 22 Apr 2025 18:56:47 +0530	[thread overview]
Message-ID: <693bafbe-5134-cf48-1e19-e47bb12ddd4f@amd.com> (raw)
In-Reply-To: <20250422132352.3988185-2-Prike.Liang@amd.com>

Reviewed-by: Arvind Yadav <Arvind.Yadav@amd.com>

On 4/22/2025 6:53 PM, Prike Liang wrote:
> The evf fence name can clearly identify the userq usage.
>
> Signed-off-by: Prike Liang <Prike.Liang@amd.com>
> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_eviction_fence.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_eviction_fence.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_eviction_fence.c
> index 0075469550b0..610f447ede9b 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_eviction_fence.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_eviction_fence.c
> @@ -31,7 +31,7 @@
>   static const char *
>   amdgpu_eviction_fence_get_driver_name(struct dma_fence *fence)
>   {
> -	return "amdgpu";
> +	return "amdgpu_eviction_fence";
>   }
>   
>   static const char *

  reply	other threads:[~2025-04-22 13:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 13:23 [PATCH 1/3] drm/amdgpu: add the evf attached gem obj resv dump Prike Liang
2025-04-22 13:23 ` [PATCH 2/3] drm/amdgpu: set the evf name to identify the userq case Prike Liang
2025-04-22 13:26   ` Yadav, Arvind [this message]
2025-04-22 13:36 ` [PATCH 1/3] drm/amdgpu: add the evf attached gem obj resv dump Christian König
2025-04-22 13:42   ` Yadav, Arvind

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=693bafbe-5134-cf48-1e19-e47bb12ddd4f@amd.com \
    --to=arvyadav@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Prike.Liang@amd.com \
    --cc=amd-gfx@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 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.